Timer and Sleep issues with system clock

[Luc Moreault <lmoreault@…>]

Hi,

I think there is an isue currently with some of the classes that use time sensitive code.

After a quick look, I found that boost::deadline_timer and this_thread::sleep() were sensitive to system clock change.

Even if using durations (instead of relative times) setting the system clock back affects those timers.

Do you know what might be the cause of such behavior (eventhough duration is used)?

Thanks

[Luc Moreault <lmoreault@…>]

Hi,

Anybody witnessed the same issue or tried to replicate it?

This can cause serious issues in some situations where the clock is set when the code is running.

Thanks

[chris_kohlhoff]

The asio::deadline_timer typedef uses the UTC clock, as documented here.

If you don't want to be sensitive to UTC clock changes then use the new asio::steady_timer typedef, or write your own custom time traits to use an alternative clock as shown in this example.

[Luc Moreault <lmoreault@…>]

Hi chris,

Thanks for the steady_timer pointer. Do you have a similar suggestion for other timing related calls? (this_thread::sleep)

Regards, Luc

[chris_kohlhoff]

You could use steady_timer's synchronous wait() function.

[anonymous]

Was that also changed in condition_variable (timed_wait)?

Thanks, Luc

[chris_kohlhoff]

Not my area, sorry.