264803 - "clear cache" in "edit>preferences>advanced>cache" delete current download files too

Status: RESOLVED EXPIRED

(Core :: Networking: Cache, defect)

Description

[Jens Borchert]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910

You are downloading a file with download manager.
While downloading go to "edit>preferences>advanced>cache" and click  "clear cache" .
The file you are downloading is deleted too and the percent progress in download
manager stops. 
You can not resume the download.


Reproducible: Always
Steps to Reproduce:
1. download a file
2.While downloading go to "edit>preferences>advanced>cache" and click  "clear cache"


Actual Results:  
Download is canceled

Expected Results:  
Do not clear files in cache currently in use.

Comment 1

[OstGote!]

WFM with Moz 1.7.3 on WinNT4. Download is not stopped or deleted, but I get the
following error in the JS console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsICacheService.evictEntries]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://communicator/content/pref/pref-cache.js :: prefClearCache :: line 89" 
data: no]

Comment 2

[benc]

-> download manager.
Download manager uses cache, not it's own temp file.

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

no, download manager does use its own temp file (look in the target directory
you chose for a file named *.part)

Comment 4

[Darin Fisher]

i wonder if this is related to bug 265028.

Comment 5

[benc]

Christian: what I meant to say... (as I understand it), the download manager
transfer still goes through cache (download the same large file twice and
compare download times!), so clearing disk cache probably while a file is being
transfered is not the greatest idea.

Comment 6

[Christian :Biesinger (don't email me, ping me on IRC)]

benc: but this code should be able to deal somehow with that. for example, not
kill the cache entry for the in-progress download. or, kill that entry, and let
the download proceed anyway.

(note: haven't tried to reproduce this bug yet)

Comment 7

[benc]

Christian: I agree with you completely, I've often felt that downloads should
not use cache at all, because in combination w/ a temp file, large downloads
have a huge footprint.

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.