Closed
Bug 211024
Opened 22 years ago
Closed 19 years ago
Large downloads stopped, but progress windows still active
Categories
(SeaMonkey :: Download & File Handling, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: timberbt, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
I started three downloads (each around 700MB) from three different sources in
Mozilla as FTP transfers. In another program I had several smaller downloads
going at the same time.
I had three download progress windows on my desktop at once all three downloads
stopped. "Elapsed Time" and "Time Left" stopped changing. Status did not
change and still reported the last transfer rate. The window itself was still
responsive, but no text was being updated. Redraws worked fine.
So I assume there are a couple possibilities:
1) My connection got broken and messed up these transfers. My other smaller
transfers never skipped a beat so I don't think that is the case
2) The three sources I was downloading from in Mozilla all failed at the same
time. Not likely.
3) Something else broke. I'm assuming this is the answer but that "something"
is a big question mark.
If the transfers were all from one spot I would have written it off as a
connection burp. But all three were from different sources (1 west coast, 2
east coast, and I am on the east coast)
If the download DID just fail....shouldn't the Elapsed time, time left, and
transfer rate be changing (i.e. shouldn't the transfer rate go to zero?)
Reproducible: Didn't try
Steps to Reproduce:
1. Start 3+ LARGE FTP downloads going
2. And wait
3.
Actual Results:
Will try tommorrow again and post results
Expected Results:
Reported an error in the download, a broken connection or whatever happened.
The download progress window should have gotten updated as well. The Elapsed
Time should keep counting and the transfer rate should be updated as well.
Only using default theme, brand new install of the latest version of Mozilla.
Download was on debian ISO files from around the USA.
I did finally get a chance to try the same scenario again. It isn't exactly a
speedy process as the downloads did not stall until a couple hours into it.
But, the behaviour was the same again.
I'm getting a similar bug in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030917
Firebird/0.6.1+
The download status just seems to freeze (the download rate, progress bar, etc
stops moving). This forces me to close it and start downloading again.
Ususaly it goes well the second time but not always.
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 3•19 years ago
|
||
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 4•19 years ago
|
||
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•