https://svn.boost.org/trac10/ticket/8534 <p> During signal invocation, we take care to unlock the signal's mutex before executing its slots, in order to avoid any possible locking order violations between the signal's mutex and whatever the user may be doing in the slot code. However, we do destroy slots while holding the signal's mutex. It would be better if we could avoid holding the signal's mutex locked while calling the slots' destructors. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/8534 Trac 1.4.3 Frank Mori Hess Mon, 13 Apr 2015 03:00:48 GMT https://svn.boost.org/trac10/ticket/8534#comment:1 https://svn.boost.org/trac10/ticket/8534#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">assigned</span> </li> <li><strong>milestone</strong> <span class="trac-field-old">To Be Determined</span> → <span class="trac-field-new">Boost 1.59.0</span> </li> </ul> <p> Should be fixed now on the develop branch </p> Ticket Frank Mori Hess Sat, 25 Apr 2015 17:14:41 GMT https://svn.boost.org/trac10/ticket/8534#comment:2 https://svn.boost.org/trac10/ticket/8534#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">assigned</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> Ticket