id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
12049	Assertion failure from detached threads during shutdown	Braden McDaniel <braden@…>	viboes	"I'm observing assertion failures coming from detached threads during shutdown (i.e., the main thread is in static destruction):
{{{
libs/thread/src/pthread/thread.cpp:149: void boost::detail::set_current_thread_data(boost::detail::thread_data_base*): Assertion `!pthread_setspecific(current_thread_tls_key,new_data)' failed.
}}}
I'm seeing this on both Linux and Mac platforms; and the problem appears to have been introduced in the 1.60.0 release; 1.59.0 did not exhibit the problem.

Stacks from these threads at the time of the assertion failure look like this:
{{{
#0	0x00007fff95104002 in __pthread_kill ()
#1	0x000000010356944e in pthread_kill ()
#2	0x00007fff9ef566e7 in abort ()
#3	0x00007fff9ef1ddc7 in __assert_rtn ()
#4	0x0000000100a4ff90 in boost::detail::set_current_thread_data(boost::detail::thread_data_base*) at /Users/mcdanb/Build/buildpackages/API/pkg_build/boost_1_60_0/libs/thread/src/pthread/thread.cpp:149
#5	0x0000000100a50141 in boost::(anonymous namespace)::thread_proxy(void*) at /Users/mcdanb/Build/buildpackages/API/pkg_build/boost_1_60_0/libs/thread/src/pthread/thread.cpp:185
#6	0x00000001035679f9 in _pthread_body ()
#7	0x0000000103567976 in _pthread_start ()
#8	0x0000000103564fbd in thread_start ()
}}}
So, the thread appears to have completed any work it was doing. The problem is not reproducible 100% of the time; but when it happens (which is not infrequent), I appear to see one assertion for each detached thread that is still present during static destruction."	Bugs	closed	Boost 1.61.0	thread	Boost 1.60.0	Regression	fixed