Closed Bug 311608 Opened 19 years ago Closed 19 years ago

While downloading 3.5GB file, progress message changes to "-1475352 KB at -184.-8 KB/sec" at some point after about 2GB have been downloaded

Categories

(Toolkit :: Downloads API, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 228968

People

(Reporter: bkasper, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

For large files, the total number of bytes downloaded (and thus the aggregate
download rate) is displayed as a negative number.  Additionally, the
floating-point download rate value is incorrectly formatted so that negative
signs are included both to the left and to the right of the decimal point.  The
number of bytes downloaded was correct until somewhere around 2GB of the file
had been downloaded (I wasn't watching so I don't know the exact point at which
the formatting changed).  Here's an example of the problem:

-14263283 KB at -174.-2 KB/sec; unknown file size


Reproducible: Didn't try

Steps to Reproduce:
1. Download a big file (> about 2GB)
2. Watch the download manager
3. I haven't tried to reproduce this, because it takes a looooong time to
download a 2GB file.

Actual Results:  
After about 2GB of the file had downloaded, the formatting of the progress text
in the Download Manager began displaying negative (and incorrectly formatted)
values for the number of bytes downloaded and the download rate.

Expected Results:  
It should have continued counting up to the full 3.5GB size of the file and
reported a correct (and correctly formatted) download rate.

*** This bug has been marked as a duplicate of 228968 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.