Boost C++ Libraries: Ticket #9720: boost::this_thread::sleep_for() sometimes returns immediately on win32

attachment set

Thu, 27 Feb 2014 09:27:51 GMT

attachment → BoostSleep_test.cpp

Test of this_thread::sleep_for and interruption.

owner, status changed

viboes — Thu, 27 Feb 2014 21:37:17 GMT

owner changed from Anthony Williams to viboes
status new → assigned

viboes — Thu, 27 Feb 2014 21:41:54 GMT

Please could you rework the example without using boost::timer and using a steady_clock or high_resolution_clock?

attachment set

viboes — Thu, 27 Feb 2014 22:02:17 GMT

attachment → test_9720.cpp

Could you try this one using the develop branch?

Sun, 02 Mar 2014 16:45:56 GMT

I've now got this happening regularly. It appears to only happen at the very start of running the program. So I've rewritten it with just chrono and no timers, and also added a python script that runs it repeatedly.

Can be found here (an svn repo): http://svn.code.sf.net/p/safir/svn/misc/boost_sleep_test/

Anyway, this now fails quite quickly on a VM like the one I described above.

Timeout!
Elapsed time: 601116317640 nanoseconds.

Will try with the develop branch "soon" (am home with sick kid atm).

Sun, 02 Mar 2014 20:40:44 GMT

I just realized what the problem is!

It's not a QPC problem after all. It's the static in steady_clock::now. I've got 50 threads trying to initialize that static variable at the same time, of course things go wrong :-)

No idea of how to fix it in an efficient manner, though.

viboes — Mon, 10 Mar 2014 18:47:37 GMT

Replying to Lars Hagström <lars@…>:

I just realized what the problem is!

It's not a QPC problem after all. It's the static in steady_clock::now. I've got 50 threads trying to initialize that static variable at the same time, of course things go wrong :-)

No idea of how to fix it in an efficient manner, though.

Do you mean the static in

    static double nanosecs_per_tic = chrono_detail::get_nanosecs_per_tic();

Could you try removing the static keyword?

  steady_clock::time_point steady_clock::now() BOOST_NOEXCEPT
  {
    double nanosecs_per_tic = chrono_detail::get_nanosecs_per_tic();

Tue, 11 Mar 2014 08:08:34 GMT

Yes, that is exactly the one I mean.

I've removed the static keyword and it works very well now.

component, milestone changed

viboes — Wed, 12 Mar 2014 22:52:28 GMT

component thread → chrono
milestone To Be Determined → Boost 1.56.0

viboes — Wed, 12 Mar 2014 22:55:37 GMT

Thanks, I have changed to Chrono. I will propose you a complete patch soon.

viboes — Wed, 12 Mar 2014 23:48:02 GMT

https://github.com/boostorg/chrono/commit/318e5f24297977d1bc126d2cd7ac65effe1cb7b7

Wed, 19 Mar 2014 07:51:30 GMT

That certainly works. Thanks!

status changed; resolution set

viboes — Sun, 27 Apr 2014 13:50:35 GMT

status assigned → closed
resolution → fixed

https://github.com/boostorg/chrono/commit/dfb7bc71c9728e5b8e9bbc0679b95a46f4cbb0ba

status, severity, type, component, version, milestone changed; resolution deleted

Smithe329 — Sat, 16 Aug 2014 04:07:22 GMT

status closed → reopened
severity Problem → Not Applicable
type Bugs → Library Submissions
component chrono → xpressive
version Boost 1.55.0 → Boost.Build-M3
milestone Boost 1.56.0 → Website 1.X
resolution fixed

If you are going for best contents like myself, simply go to see this site all ekebkcegekkdbdde

anonymous — Sat, 31 Jan 2015 04:42:18 GMT

When are you guys going to fix it?

type, version, component, severity, milestone changed

viboes — Sat, 31 Jan 2015 09:59:17 GMT

type Library Submissions → Bugs
version Boost.Build-M3 → Boost 1.55.0
component xpressive → thread
severity Not Applicable → Problem
milestone Website 1.X → To Be Determined

Smithe329, we can be wrong when we do some changes on the Trac. This doesn't mean that you don't need to be polite.

viboes — Sat, 31 Jan 2015 10:02:54 GMT

It seems this is related to #9856 and #10967.

status changed; resolution set; milestone deleted

viboes — Sun, 01 Feb 2015 15:23:28 GMT

status reopened → closed
resolution → fixed
milestone To Be Determined

anonymous please, if this is not working for you give more information. This was fixed as Lars said "That certainly works. Thanks!".