Closed
Bug 143055
Opened 22 years ago
Closed 22 years ago
Download of very large files hangs Mozilla
Categories
(Core Graveyard :: File Handling, defect)
Tracking
(Not tracked)
People
(Reporter: norrisboyd, Assigned: law)
Details
I often download very large files (~160Mb) using my browser. When I attempt to download using Mozilla, the download proceeds fine until it appears almost done. Then machine performance becomes exceptionally slow and I often get messages about running low on virtual memory. Eventually I'm forced to kill Mozilla. Does the download process use memory proportional to the size of the download? Is that why I appear to run out of memory? The downloads work fine using IE :-(
Comment 1•22 years ago
|
||
Using 2002041711, I tried to re-create this problem with a 600MB iso file on a WINXP PC. I wasn't able to trigger it, though. I have 256 MB of RAM with 2 Gig of Virtual Memory. Perhaps I need to download a 2.5 Gig file? I did notice that memory did seem to disappear over the course of the download, even when I wasn't actively working on the PC. The only problem I had was at one point when it was 1/4 way through, I received an alert. (426 Data Connection: Bad File Descriptor) I clicked ok and the file continued to download. I wonder if that's just the file I was downloading. (RH 7.3 cd 1 iso off of a mirror) Hope this helps, Robert
Comment 2•22 years ago
|
||
To file handling... we have other reports of unbounded memory growth while downloading.... :(
Assignee: blaker → law
Component: Download Manager → File Handling
Whiteboard: DUPEME
Comment 3•22 years ago
|
||
Should be fixed in a newer build. Duping *** This bug has been marked as a duplicate of 91795 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUPEME
Comment 4•22 years ago
|
||
marking verified as a duplicate. if you decide to reopen this bug, please clarify why. search string for bugspam removal: SalviaGuaranitica
Status: RESOLVED → VERIFIED
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•