Closed Bug 842967 Opened 8 years ago Closed 8 years ago
Refresh driver may re-target the same timestamp
PreciseRefreshDriverTimer::ScheduleNextTick may target a timestamp which was already targeted on previous scheduling. One possible reason is the timer filter which skews the oneshots delay (bug 590422 suggests to get rid of that filter), which may cause an early return, or even way-too-early return (I've seen numbers > 20ms too early). But even if the filter is removed, we should still guard against such cases.
Attachment #715967 - Flags: review?(vladimir)
Attachment #715967 - Flags: review?(vladimir) → review+
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.