Cannot recover from damaged queue.xml

[robabo]

While downloading files with Filezilla, my C: harddrive got full. When I terminated Filezilla, this resulted in a incompletely saved queue.xml file (see attachment). After restoring additional space on drive C:, Filezilla was not able to recover from the damaged file.

When starting Filezilla, it complaines that the file cannot be rad/parsed.

When terminating Filezilla, it complains that the file cannot be read/parsed, and did not save the current queue, which was then completely lost.

I had to manually delete the queue.xml to make Filezilla working again.

Filezilla should be able to recover by itself. For example, it could ask the user if it should overwrite the damaged queue.xml file during save, or it could automatically overwrite it during save. At termination, I don't see why Filezilla must read the queue.xml before it is saving the queue, the content will be overwritten anyway.

[robabo]

queue.xml and error message

[Tim Kosse]

This is by design. To avoid further data loss it lets the user repair or delete the damaged file.

At termination, I don't
see why Filezilla must read the queue.xml before
it is saving the queue, the content will be overwritten anyway.

Wrong. You can have FileZilla running multiple times. Each time you close one instance, it adds items to queue.xml, and for that it needs to read it first.