Re: [Boost-bugs] [Boost C++ Libraries] #11275: Deadlock when destroying continuation future

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11275: Deadlock when destroying continuation future
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2015-06-01 17:29:57

#11275: Deadlock when destroying continuation future
-------------------------------------+-------------------------------------
  Reporter:  Konrad Zemek            |      Owner:  viboes
  <konrad.zemek@…>                   |     Status:  assigned
      Type:  Bugs                    |  Component:  thread
 Milestone:  To Be Determined        |   Severity:  Problem
   Version:  Boost 1.58.0            |   Keywords:  continuation deadlock
Resolution:                          |  destructor
-------------------------------------+-------------------------------------

Comment (by viboes):

 Replying to [comment:4 Konrad Zemek <konrad.zemek@…>]:
 > The same deadlock happens in develop (e39703f).
 >
 > I "solved" it for testing purposes by reordering variable initialization
 in {{{do_continuation}}}, but it's obviously the wrong way: if the
 future's destructor happens-before relocker's destructor, then relocker
 locks an already destroyed mutex:
 >

 I need to check if this situation is possible. Thanks for signaling it.

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