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.