Closed Bug 245203 Opened 20 years ago Closed 20 years ago

Mozilla stops responding when saving a large file to a network drive.

Categories

(Toolkit :: Downloads API, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 69938

People

(Reporter: alphawolf_, Assigned: bugs)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Build Identifier: 

When you download a large file and save it to a network drive, firefox will 
lock up for a very long time, depending on the size of the file.

Reproducible: Always
Steps to Reproduce:
1. Find a large file (try this: 
http://www.linuxiso.org/download.php/570/install-x86-universal-2004.1.iso)

2. Download it to a network drive (presumably SMB/windows file share)

3. When the download finishes, prepare to be annoyed.

Actual Results:  
Mozilla stops responding.

Expected Results:  
I would expect mozilla to either save the file directly to the network drive 
(instead saving to temp, then moving to the destination,) or if that can't be 
done, firefox should not freeze while it is moving the file to the network 
drive (e.g. you should still be able to browse webpages while it is doing this)

Maybe even add a nice progress indicator or something so that you know when it 
will be done moving the file across the network.


It seems that Firefox downloads the file to a temp directory on the local C 
drive, and as soon as it's finished downloading, it moves it over to the 
network drive afterwards. If you have a slower network (e.g. a 11mbit wifi 
card) this can take a very long time if you download a very large file, such as 
this one:

http://www.linuxiso.org/download.php/570/install-x86-universal-2004.1.iso

*** This bug has been marked as a duplicate of 69938 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Bug 69938 is the real cause, but the bug for the Mozilla lock during
moving is bug 103766. Copy a large file should not freeze Mozilla.
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.