Closed
Bug 43789
Opened 24 years ago
Closed 24 years ago
Timers do not fire accurately
Categories
(Core :: XUL, defect, P2)
Tracking
()
VERIFIED
FIXED
M17
People
(Reporter: pavlov, Assigned: pavlov)
References
Details
(Keywords: perf, platform-parity, regression, Whiteboard: [dogfood-][nsbeta2+])
Attachments
(1 file)
|
(deleted),
patch
|
Details | Diff | Splinter Review |
Due to the fix checked in for bug 34871, timers no longer fire accuratly. This
is partially due to an PRUint32 overflow and partially due to us no longer
resetting timers time-to-fire, so "NOW" is always greater than when the timer
was supposed to fire, so it fires every time the timer queue gets processed
(every 10ms). We also were not firing with ms accuracy, but instead rounded to
the nearest second.
|
Assignee | |
Updated•24 years ago
|
Severity: normal → blocker
Status: NEW → ASSIGNED
Keywords: dogfood
Priority: P3 → P2
Target Milestone: --- → M17
|
|
Assignee | |
Comment 1•24 years ago
|
||
|
||
Comment 2•24 years ago
|
||
cc me
|
|
Assignee | |
Comment 3•24 years ago
|
||
things that the user might notice:
* the caret in text fields blinking 100 times/sec
* pages with dhtml using timers are horifically slow. (see test13 or bug 12761)
|
|
Assignee | |
Updated•24 years ago
|
Summary: Timers do not fire accuratly → Timers do not fire accurately
|
||
Comment 4•24 years ago
|
||
Adding myself to CC, adding regression and patch keywords.
|
|
Assignee | |
Updated•24 years ago
|
Blocks: 43684
Keywords: patch,
regression
|
||
Comment 6•24 years ago
|
||
Seems like a good bug to fix for beta, but not sure why it's dogfood, based on
the symptoms described.
Whiteboard: [dogfood-][nsbeta2+]
|
|
Assignee | |
Comment 7•24 years ago
|
||
checked in fix
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
|
||
Comment 9•24 years ago
|
||
Adding keyword to bugs which already show a nsbeta2 triage value in the status
whiteboard so the queries don't get screwed up.
Keywords: nsbeta2
You need to log in
before you can comment on or make changes to this bug.
Description
•