Re: [Boost-bugs] [Boost C++ Libraries] #2330: thread::interrupt() can be lost if condition_variable::wait() in progress

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #2330: thread::interrupt() can be lost if condition_variable::wait() in progress
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-08-23 09:16:57

#2330: thread::interrupt() can be lost if condition_variable::wait() in progress
---------------------------------------+-------------------------
  Reporter:  Don Ward <don2387ward@…>  |      Owner:  anthonyw
      Type:  Patches                   |     Status:  closed
 Milestone:                            |  Component:  thread
   Version:  Boost 1.41.0              |   Severity:  Showstopper
Resolution:  fixed                     |   Keywords:
---------------------------------------+-------------------------

Comment (by anonymous):

 In our projects, a similar case occured with boost 1.55. We create a new
 thread to do something every 10 seconds. If the last thread dosn't finish,
 interrupt it before creation. After some time, we found that the creator
 dosn't run any more after call interrupt. Restart the process, it run well
 again. It is a pity that we don't dump the stack for some reason, so can't
 determine what occured on earth. Does this bug be repaired completely? Or
 it appears again in boost 1.55?

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