Closed Bug 185738 Opened 22 years ago Closed 22 years ago

Downloading files are duplicated in CACHE dir and TEMP dir, filling up hard drive

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 55307

People

(Reporter: bozo, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 When downloading some 100MB movies from http://bmwfilms.com, Mozilla managed to fill up my temp (D:) drive. I discovered that it was saving a copy in the Mozilla CACHE dir (D:\MozCache ...), and in TEMP (D:\temp\). I told it to download to G:\ I know it normally saves to TEMP, and then copies to the destination when it's done, but I don't think it's reasonable for it to also save to the CACHE, esp. when I have the cache set to 50MB max. My D: drive had 190MB free, and it got filled trying to d/l 1 100MB file. Thanks Reproducible: Always Steps to Reproduce: 1. put CACHE and windows TEMP (temp=d:\temp) on a small drive/partition. 2. download a file sized at least 51% of free space 3. PROFIT! :) Actual Results: Download manager said it failed to write to d:\temp\filename due to disk full... Expected Results: don't store d/l's in both CACHE and TEMP
also reported in bug 141790 and others, dup of bug 69938 *** This bug has been marked as a duplicate of 69938 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
I'm sorry, but this is not quite the same as http://bugzilla.mozilla.org/show_bug.cgi?id=69938 My point is the file should not go into CACHE, ESP IF IT'S BIGGER THAN CACHE MAX SETTING! Thank you, Barry
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
*** This bug has been marked as a duplicate of 55307 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.