Closed
Bug 331732
Opened 19 years ago
Closed 16 years ago
When update download speed is > 1.0MBps, time remaining is incorrect
Categories
(Toolkit :: Application Update, defect)
Toolkit
Application Update
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: rishi.maharaj, Unassigned)
Details
(Whiteboard: closeme 2009-04-16)
Attachments
(1 file)
|
17.40 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060322 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060322 Firefox/1.6a1
When an update is being downloaded at any speed greater than 1.0MB/sec, the time remaining counter is obviously incorrect (see screenshot).
Reproducible: Always
Steps to Reproduce:
1. Check for Updates.
2. Download an update at > 1.0MBps
Actual Results:
The time remaining counter shows an unreasonably large amount of time.
Expected Results:
The time remaining counter shows the quotient of the data left to download and the transfer.
| Reporter | ||
Comment 1•19 years ago
|
||
Comment 2•18 years ago
|
||
I'm seeing this on mac intel trunk 2007061504. It shows a time estimate in excess of an hour, and the estimate drops very quickly from there. Looks like we're estimating the time as though it's 1 KBps.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
| Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
Comment 3•17 years ago
|
||
With the landing of bug 414326 we now use the same methods for displaying progress as the download manager. Can you check against current trunk to see if this is still reproduceable? Thanks
Comment 4•16 years ago
|
||
Can someone check if this is still reproducible with either a Minefield (e.g. mozilla-central) or Shiretoko (e.g. mozilla-1.9.1) nightly? Thanks
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/
Whiteboard: closeme 2009-04-16
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•