Closed Bug 263807 Opened 20 years ago Closed 19 years ago

Download 2 large file simultaneously failed and status display wrong in Download Manager

Categories

(SeaMonkey :: Download & File Handling, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: chenxq, Unassigned)

Details

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

Browser Version: Mozilla 1.7.2
My browser Preferences:
Http Proxy: 192.168.9.2  Port: 80  (my company's local area network)
Proxy Server: Microsoft ISA Server
Operation System: Windows XP chinese version

I used mozilla browser to download a video chip from URL:
http://oxygen.lcs.mit.edu/videos/collaboration.mpeg. First it started
downloading normally, at speed 3k/s ~ 5k/s. From list view of download manager
dialog, that file sized 81008 KB, a big file for me. The transfer speed between
mit website and my pc is slowly. So I waited patiently. 
Later I download another file from URL: 
http://www.alice.org/downloads/authoringtool/2004_09_15_pm/Alice.zip. Download
manager told me that file size is 63488KB, the initial transfer speed was about
1M bps, but the speed droped a little by little. Alice.zip downloaded size
reached to about 5M bits and the speed kept on about 300k bps. So you can see
,there were two simultaneous download activities at that time, one quick ,the
other slow. 
But an error happened, Alice.zip download activities seemed stopped,for the
downloaded size didn't increase and speed froze at 300kbps, never change. So did
collaboration.mpeg download activity. Both were stopped and frozen. I don't know
why. This situation existed about 15 seconds and another error happened.
Download manager first set Alice.zip progress status to Finished, Transfered
size to 81008 KB. Obvious download manager made mistake, because the download
was incomplete and actual download size is about 5M bits not 63488KB. 

I don't know weather it is network data transfer error that cause browser's
Download Manager made such bug. Before I have met the same bug. This time it
recured. So I think it's necessary to tell you, the great development team about
it. Hope this infomation is useful for you.


Referrence bug ID: 236456

Reproducible: Sometimes
Steps to Reproduce:
1.set browser preference to proxy mode
2.download first larget file, 
3.download second larget file
4.wait them complete
Actual Results:  
Download manager wrongly point out that 2 file download complete, in fact part
of file is download, not whole. So I can't open the downloaded file.

Expected Results:  
Should let download complete and I can open the downloaded file.
Product: Browser → Seamonkey
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/
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.