User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 If you check preferences->advanced->cache, you can set a disk space limit for the cache. On Linux, this limit is not honored. Example: Download a game demo with 100MB. The cache grows to 100MB first, then after download Mozilla realizes 'oops, this is more than 5 MB', and throws the cached copy away. The reason to report a bug is this: a) If I say 5 MB cache, this means 5 MB. Not 'store 100Megs first and see if that fits the cache'. IF Mozilla simply caches everything, it should check DURING download if the file exceeds the cache limit, and if it does, it just should delete the cache entry. b) The cache is not the place to put a 100MB demo. The cache should be for stuff that is likely to be downloaded again, like background images and such. A user normally doesn't download a game demo 3 times in a row. So: big files usually do not need caching. c) I have 60 Gig of disk space, and can't still download anything larger than 60Meg. Why? My home dir is on a small partition (this is good practice, so users care more about what space they waste -- ext3 doesn't allow quota). Since Mozilla caches all downloads, the cache will grow to 60 Meg, and surprise, at this point my filesystem is full. Bad luck for me. d) hidden cache: mozilla downloads the file to $TMP first, and moves it uppon completion of the download. This further reduces my download limit to 30 Megs (30 Megs in cache, 30 Megs in $TMP = 60 Megs). I can, of course, set my $TMP to another partition, so this is more like a minor nuisance (you usually don't remember to set $TMP to a data dump partition befor you start your browser). Reproducible: Always Steps to Reproduce: 1. Download game demo that exceeds free disk space 2. Download aborts. 3. No resume option for download means: all tranfered data was worthless. Actual Results: My partition was full. Not full of eels, but full of garbage (since there's no resume options). Expected Results: No cached copy of the downloaded game demo. Maybe data which exceeds a customizable maximum size should not be cached on a general basis. It should have resumed the download under windows (copied the file to there and tried to resume). Mozilla: "The files already exists. Overwrite? (Ok) (Cancel). I rate this bug major since it reprives the privilege to download large files if the partition is small, but there's much space available on other disks. I understand that on NFS systems where your homedir is just 15 Megs and quotaed, it is impossible to save stuff to the /usr/tmp which is a local hard disk unter Solaris. I rate the cache implementation broken in a semantic way. Since the cache is a major feature, it's a major bug.

see bug 69938, bug 74085, bug 103877. Resolving as dup of bug 55307 *** This bug has been marked as a duplicate of 55307 ***