Failed downloads not removed from active downloads array

VERIFIED FIXED in mozilla1.9alpha8



11 years ago
10 years ago


(Reporter: mak, Assigned: reed)



Windows Vista
Bug Flags:
in-litmus +

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [good first bug])


(1 attachment)

I had tried to download a no more existent file from the web, i ended up with 3 failed and 1 cancelled downloads (i clicked retry and cancel, one time). notice that it's the same file, so i was expecting to only get one entry instead of 4, is this by design?

Now when i ask to exit Firefox i get "If you exit now, 4 downloads will be cancelled"... those are already failed or cancelled, so the dialog should not warn me, i have no downloads in progress. 
I tryed to find a dupe but i can't

Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007082415 Minefield/3.0a8pre
if you can get me a reproducible test case for this, I can fix it, but I haven't been able to reproduce this (but I have heard of reports of this, so I'm not denying that it exists).
Keywords: qawanted

Comment 2

11 years ago
i have found this in this way, i have no time now to find more correct steps, probably they are not all needed

1. start with an empty profile (empty folder, so it's recreated on launch) [maybe optional] and use only the starting tab (no other tabs)
2. go to and search pdf
3. find "[PDF] UNIX: introduzione elementare" right click on link and choose save as
4. save to desktop
5. the download fails with an error dialog, repeat steps 3 & 4 a couple of times without waiting for error dialog (is this error dialog by design?)
6. close the download manager, then close Firefox

i think that point 3 and 4 (repeated a couple of time) should be enough to reproduce, i'll try to find better steps in the next days, if this does not help

Comment 3

11 years ago
mh that download works now so i cannot reproduce with that link... before i was getting an error dialog, probably the server was temporarly down... i'll try to find another link to test...
Yes, that looks to be about all we are missing.


11 years ago
Keywords: qawanted
Whiteboard: [good first bug]
Litmus test would need to try a download that will fail.
Flags: in-litmus?
Flags: blocking-firefox3?
Target Milestone: --- → Firefox 3 M8


11 years ago
Depends on: 103487
Keywords: regression
Summary: Cancel downloads dialog on quit should not be fired with only failed/cancelled downloads → Failed downloads not removed from active downloads array


11 years ago
Duplicate of this bug: 393519

Comment 8

11 years ago
Created attachment 278147 [details] [diff] [review]
patch - v1

As you say...
Assignee: nobody → reed
Attachment #278147 - Flags: review?(comrade693+bmo)


11 years ago
Attachment #278147 - Flags: review?(comrade693+bmo) → review+

Comment 9

11 years ago
maybe i've found a simple way to reproduce, using a not existant domain, try to download this with Save As:


i have tested your suggested fix in comment #4 and it works.

On failing i get an error dialog, telling me that the file cannot be downloaded because the source is no more available, this is an annoyance, why should i get a dialog, i already see the FAILED indicator in the dm, i'd prefer to have some way in the dm to see why it failed. 
What if i download a bunch of not existant files, have i to click OK on all dialogs? 
Is this the correct behaviour or should i fill another bug to search for a better solution in showing download errors?
No longer depends on: 103487
Keywords: regression
Summary: Failed downloads not removed from active downloads array → Cancel downloads dialog on quit should not be fired with only failed/cancelled downloads


11 years ago
Depends on: 103487
Keywords: regression
Summary: Cancel downloads dialog on quit should not be fired with only failed/cancelled downloads → Failed downloads not removed from active downloads array

Comment 10

11 years ago
Checking in toolkit/components/downloads/src/nsDownloadManager.cpp;
/cvsroot/mozilla/toolkit/components/downloads/src/nsDownloadManager.cpp,v  <--  nsDownloadManager.cpp
new revision: 1.107; previous revision: 1.106
Last Resolved: 11 years ago
OS: Windows Vista → All
Hardware: PC → All
Resolution: --- → FIXED

Flags: in-litmus? → in-litmus+
OS: All → Windows Vista
Hardware: All → PC

Comment 12

11 years ago
ehy stephen, the litmus test is not valid, you should use comment #9 link, maybe an html with such a link in it...
Will not work using original steps, since the link was temporarly invalid, while now it's valid and cannot be used to reproduce

the only steps are
1. try to download with save as the link http://www.domain.fake/not_existant_document.pdf
2. wait for the download to fail
3. close the DM
4. close the browser

Expected Results:
the quit dialog does not complain about losing in progress downloads

You also shouldn't need a clean profile.  It would have happened all the time.
Litmus testcase fixed; can you guys refresh and let me know?


Comment 15

11 years ago
s/DM/Download Manager/

it's ok, i've tried to follow steps with current nightly and it fails, while it was fine with custom build (including the fix)
I'm going to spin off a bug that, when you right-click and try to save that non-existent PDF file, although you get the "...could not be saved, because the source file cannot be read..." alert ("not_existant_document.pdf [sic]"), the bogus file's entry isn't populated until you close and reopen the DM window; oddly enough, successive files (if you repeat the steps) seem to populate their entries correctly.  What happens, instead, is that the "Active--------" section appears, but with no entries.

Anyway, I'm splitting that off because one can still exit cleanly without any bogus "Downloads in progress" warning message.

Verified FIXED using Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9a8pre) Gecko/2007082618 Minefield/3.0a8pre on Windows Vista, Mac OS X 10.4, and Fedora Core 7.
I filed bug 393821 to get a cleaner bug.
Flags: blocking-firefox3?
Blocks: 103487
No longer depends on: 103487
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.