Re: [Boost-bugs] [Boost C++ Libraries] #8006: Boost::Chrono Assertion at startup - steady_clock::now() - Windows

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #8006: Boost::Chrono Assertion at startup - steady_clock::now() - Windows
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-07-31 21:14:05

#8006: Boost::Chrono Assertion at startup - steady_clock::now() - Windows
-------------------------------+----------------------
  Reporter:  meckschlager@…    |      Owner:  viboes
      Type:  Support Requests  |     Status:  reopened
 Milestone:  To Be Determined  |  Component:  chrono
   Version:  Boost 1.50.0      |   Severity:  Problem
Resolution:                    |   Keywords:
-------------------------------+----------------------

Comment (by anonymous):

 I've hit this assertion as well (Boost 1.55, VS 2013, Windows 10 64-bit)
 by trying to acquire a shared mutex for a limited period of time (1 ms).
 Here was the callstack:

 1. steady_clock::now()
 2. shared_mutex::try_lock_shared_for()
 3. shared_lock::try_lock_for()

 Although obviously not thread-safe, it didn't look to me that the
 assignment of the return value of chrono_detail::get_nanosecs_per_tic() to
 the static variable nanosecs_per_tic was the cause of the problem since
 nanosecs_per_tic had a positive value (about 311) at the time of the
 assertion.

 This implies that the problem must have been with the return value of
 winapi::QueryPerformanceCounter() to which I didn't have access.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/8006#comment:31>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.