Closed Bug 1140570 Opened 9 years ago Closed 9 months ago

after improper shutdown firefox deletes completed download

Categories

(Firefox :: Downloads Panel, defect)

36 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: freddi34, Unassigned)

Details

(Keywords: dataloss)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150224133805

Steps to reproduce:

1. A quite large file (1GB) was successfully downloaded and the download completed (yesterday).
2. Since then Firefox had been closed and later opened again like during normal computer use (today).
3. The computer had to be restarted improperly (today).
4. Firefox was opened again, although connection to internet was not yet available.


Actual results:

When opening firefox, it attempted to respawn the download (as if it had no completed). The download failed du to lack of internet connection. Firefox deleted the supposedly failed download.

This is a critical issue because I don't use a browser with the risk of it quietely accessing my personal files and arbitrarily deleting files. This case was also a big disappointment because I downloaded the large file exactly for the time when I had no internet and when I needed it, and knowing the download had completed I was sure I would have the file.


Expected results:

When restarting Firefox, it should not have respawned a download that was completed successfully. Even if Firefox resets to an earlier time due to a potentially corrupted configuration file, this should under no circumstances lead to data loss of this extent.

When attempting to delete failed downloads, Firefox should ask the user to confirm. Sometimes the user may want to have a file even if the download didn't incomplete.

When deleting files, Firefox should consider not circumventing the trash, to make files easier to recover.
Severity: normal → critical
QA Whiteboard: [bugday-20150309]
Keywords: dataloss
Component: Untriaged → Downloads Panel

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --

The severity field is not set for this bug.
:mak, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(mak)

It's unclear why a successfully downloaded file would have been restarted on the next session, and after 9 years the code has changed so much that I feel like it's not worth trying to debug it without a more recent happening of the same bug.

Status: UNCONFIRMED → RESOLVED
Closed: 9 months ago
Flags: needinfo?(mak)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.