242679 - Downloads are cached as well as being stored in temporary items, and so you need lots of free disk space.

Status: RESOLVED DUPLICATE of bug 55690

(Toolkit :: Downloads API, defect)

Description

[Josh Watson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

When I try and download a 500 meg file, the download fails because the file is
stored in Local Settings\Temp (in my windows profile) and also in the Mozilla
cache, as this grows at a similar rate to the temporary download file. 

This is also bigger than my 50 Mb cache limit.

Mozilla then tries to move (hopefully not copy!) the file to the location I
specified from Temp, so I need at least 1Gb free disc space (on my system drive)
to download a 500 meg file. 

If I don't want to d/l the file to my system drive (which I don't), I need 1 Gb
of Space on my system drive and 500 Mb on my personal drive. So 3x the space for
the file!

Reproducible: Always
Steps to Reproduce:
1. Download a big file with not much disc space free
2. Have a look in Local Settings\Temp in your Windows profile (on Windows 2000)
3. Have a look in Application Data\Phoenix\Profiles\<your Moz profile>\<random
letters>\Cache - it'll be as big as the download
4. Weep as you can't play Tribes II :)
Actual Results:  
I ran out of disk space as the software keeps at least 2 copies of a big
download on the system drive. I have more than enough space at the target drive
for the location.

Expected Results:  
Not cached it, and also created the temporary item where I specified to download
the file (say in <specified filename>.mozillapart). Then, just rename this when
the download is complete, like Getright. IE doesn't do this either, but then
FireFox is better than IE :)

Comment 1

[Josh Watson]

Just another quick note to say that the figure in "Disk Cache: Storage in use:"
in about:cache seems to spin around a few values as this is being downloaded,
which is weird 1376xxxk -> 3287xxxk -> etc. all of which are incorrect.

Comment 2

[OstGote!]

Storing in cache is Bug 55307, storing in tmp is Bug 69938.

The tmp bug is now not so severe because we move the file when the destination
is selected with current builds (see bug 55690).

IMO you could dupe your bug against one of the above bugs.

Comment 3

[Ali Ebrahim]

This is a dupe of bug 55690, which was fixed post-Firefox 0.8 (and solves the
problem of the file being stored in the cache and the temporary items).

If you upgrade to a current nightly build this problem should go away.

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

Comment 4

[OstGote!]

(In reply to comment #3)
> This is a dupe of bug 55690, which was fixed post-Firefox 0.8 (and solves the
> problem of the file being stored in the cache and the temporary items).
The cache problem is still not fixed, see Bug 55307.

Comment 5

[Ali Ebrahim]

(In reply to comment #4)
> (In reply to comment #3)
> > This is a dupe of bug 55690, which was fixed post-Firefox 0.8 (and solves the
> > problem of the file being stored in the cache and the temporary items).
> The cache problem is still not fixed, see Bug 55307.

Yes, I realise this. But bug 55690 was about the temp file being stored in the
cache and the tmpdir at the same time. Bug 55690 does not fix bug 55307, you're
right about that. But it does fix the situation where its stored in the cache
and tmpdir simeltaneously, which is what this bug is about.