74739 - downloading filled up c: even told to save to other drive letter

Status: VERIFIED DUPLICATE of bug 55690

(Core Graveyard :: File Handling, defect)

Description

[c.h.ip]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; 0.8.1) Gecko/20010323
BuildID:    0.8.1 2001032319

I tried to download Mandrake 8.0 beta 3 (2 ISO CDs) using Mozilla, when I
started downloading, Mozilla asked me where will I put the downloaded files, I
choose a directory in F:.

However, during the downloading process, drive C: (where the user
profiles/settings are stored) is still filled up with the temporary downloaded
files and the location of F: does not have any new files.

Because my C: doesn't have 1.4G of free disk space, the download process must to
be canceled to free up the disk space.

As I understand this is the mechanism of Mozilla for downloading files, it seems
unreasonable, even my f: have plenty of space to store downloaded files, the
capacity of my download is limited to how much disk space remains on c: (where
user profile is located), even mozilla is not installed on drive c: (also of my f:)

Reproducible: Always
Steps to Reproduce:
1. Fire up mozilla
2. Try to downloading something using ftp, which the filesize is more than the
free disk space of your c:, specify to save it into another drive.
3. see what happens (c: will be filled up)

Actual Results:  download process holds when c: is completely filled up

Expected Results:  some part of downloaded files should be placed of another
drive specified, freeing up disk spaces on c:


I'm not sure if Linux/Mac builds will behave like this.

Comment 1

[Andreas Franke (gone)]

*** Bug 74737 has been marked as a duplicate of this bug. ***

Comment 2

[Boris Zbarsky [:bzbarsky]]

Actually, the issue is that the Windows temporary directory in on the C: drive
on your computer... Mac and Linux would behave the same way if the temporary dir
were on a drive with little free space.

Try setting TEMP to someplace on F:

Comment 3

[Keyser Sose]

This is a problem in Windows not our problem (windows sets the temp directory).
Marking Invalid.

Comment 4

[Doug Turner (:dougt)]

Ahh.  No, this bug is NOT invalid.  For whatever reason, someone decided to 
download to the temp directory first, the copy to the destination.  Because of 
this, download require (in some cases) twice the ammount of diskspace.

We should do what the users asks: download to the download destination - avoid 
the download to temp and copy.

Comment 5

[Boris Zbarsky [:bzbarsky]]

The reason we download into the temp directory is because we start the download 
before the download filename has been entered.... see bug 55690

Comment 6

[Doug Turner (:dougt)]

to law

Comment 7

[Bill Law]

This is just another manifestation of bug 55690, I think.

*** This bug has been marked as a duplicate of 55690 ***

Comment 8

[benc]

qa to me -> general networking
VERIFIED:
Doesn't sound like FTP has different behavior, all badness is in bug 55690.