720490 - nsIdleService runs with too low internal resolution in its calculations

Status: RESOLVED WORKSFORME

(Core :: Widget, defect)

Description

[Mike Kristoffersen (:MikeK)]

The nsIdleService runs use a one second resolution in it's internal calculations, which is too little is it should support a one second resolution on its external interface as one could expect since you can ask for it with a one second resolution.

(This is probably also what makes some of the failures on bug 517482 as that test only allows for max 1 second offset to the correct idle time.

Comment 1

[Justin Lebar (not reading bugmail)]

While you're fixing this, please fix nsIdleService not to use PR_Now().  PR_Now is not suitable for intervals.

This is a serious bug on any system which automatically changes its clock -- in particular, this applies to mobile devices, which sync their clocks via the radio.

Comment 2

[Mike Kristoffersen (:MikeK)]

(In reply to Justin Lebar [:jlebar] from comment #1)
> While you're fixing this, please fix nsIdleService not to use PR_Now(). 
> PR_Now is not suitable for intervals.
> 
> This is a serious bug on any system which automatically changes its clock --
> in particular, this applies to mobile devices, which sync their clocks via
> the radio.

This should be covered by bug 555313

Comment 3

[Mike Kristoffersen (:MikeK)]

While testing a solution to this I have found that the lack of resolution isn't the only explanation to the random orange in bug 517482.  It needs further investigation.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

Comment 5

[Stephen A Pohl [:spohl]]

Bug 517482 was resolved. Closing this bug.