Abrupt response of a download after two instances of that download have already been cancelled

RESOLVED EXPIRED

Status

--
major
RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: rupendradhillon, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040421

If we cancel and then "remove from list" two instances of download of a single
and restart the download again for the same file then that download would have
the same abrupt behavior as shown by the two earlier downloads as explained in
bug 241678.

Reproducible: Always
Steps to Reproduce:
1. Start downloading the same file in two different locations on the PC
2. Cancle both the downloads.
3. Restart the download again

Actual Results:  
The file's downloaded status will keep on shifting back and forth until the
download completes.

Expected Results:  
The download should not give such abrupt results while it is going on.

One of the reasons behind this could be that a copy of bothe the old instances
of the files is still in the cache.

related bugs
1. 241678

Comment 1

15 years ago
dup of bug 157548?
(Reporter)

Comment 2

15 years ago
Note that this bug specifically points at what happens when the new download is
started when both the earlier downloads were cancelled and removed from the list. 

Even though the two downloads are not present now they (their copy in the
memory) somehow affects the new download also.
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.