Corrupted File Downloads Through Firefox Browser Often Occurs
Categories
(Firefox :: Downloads Panel, defect)
Tracking
()
People
(Reporter: u692448, Unassigned)
Details
Steps to reproduce:
Downloaded files via file hosting sites or via cloud storage through Firefox browser. Very often, files come out corrupted upon competition of download.
Actual results:
Nowadays, I download the same file multiple times to compare their checksums to see if I get 2-3 identical matches to be more certain that it turned out fine. This is an extremely tedious and troublesome task, and a waste of bandwidth and time, especially when some files like video footage shot from a high-end camera for film production can be extremely large (25-100 GB per file) and it needs to be shared and downloaded multiple times by a number of group members that are working on the film project to compare checksums to see if they match. In our case, we provide the checksums for the files before uploading to the cloud, so our members can check against it after they've downloaded the file to ensure none of the frames in the footage are corrupted.
However, in most cases, the problem arises when Firefox users download something online that often doesn't have checksum they can check against. Even if they downloaded the same file two times with their checksums matching, it doesn't 100% guarantee that they aren't corrupted, since the same piece in each of the two files could be corrupted at the same spot, although very unlikely but still a possibility. Everyone in our group has very stable internet connections via ethernet cable, and not WiFi.
Expected results:
Downloaded files should not come out as corrupted. More checks should be in place during the download process to prevent such a thing.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Downloads Panel' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
Marking this as Resolved > Incomplete since the reporter cannot be contacted for further details.
Please re-open or file a new issue if it's still reproducible on your end.
Description
•