Opened 11 years ago

Last modified 11 years ago

#3611 closed Bug report

Cannot recover from damaged queue.xml

Reported by: robabo Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: robabo, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

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.

Attachments (1)

queue.rar (10.4 KB) - added by robabo 11 years ago.
queue.xml and error message

Download all attachments as: .zip

Change History (2)

Changed 11 years ago by robabo

Attachment: queue.rar added

queue.xml and error message

comment:1 Changed 11 years ago by 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.

Note: See TracTickets for help on using tickets.