id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
9787,[windows] Small duration value passed down to basic_timed_mutex::try_lock_until and condition_variable::wait_until can cause infinite or near infinite wait for win32,Bryan Laird <bryan_laird@…>,viboes,"Creating a unique_lock using a timed_mutex which is passed a small chrono::milliseconds duration value (10 milliseconds in our case) can cause a very large value to be passed to WaitForSingleObject for the dwMilliseconds parameter.  The code path creates an initial chrono::time_point where the duration value is added to the current time.  Once it gets to try_lock_until it calculates a new rel_time duration to feed to WaitForSingleObject.  If the small duration has elapsed due to thread switching then the subtraction results in a very large positive value to be passed to WaitForSingleObject.
 
Similarly, if we calculate our own boost::chrono::system_clock::time_point and pass it to boost::condition_variable::wait_until and the time_point has passed then the subtraction to compute a relative time value can result in a very large positive value.  Another possibility is if the caller inadvertently passes an elapsed time_point to condition_variable::wait_until.",Bugs,closed,Boost 1.57.0,thread,Boost 1.53.0,Problem,fixed,WaitForSingleObject timed_mutex try_lock_until wait_until,