id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
529	BOOST_SP_USE_QUICK_ALLOCATOR and BOOST_AUTO_UNIT_TEST	alexey_martynov	Peter Dimov	"{{{
When using BOOST+AUTO_UNIT_TEST and
BOOST_SP_USE_QUICK_ALLOCATOR and BOOST_HAS_THREADS
macros under Windows (MSVC71) Access Violation occurs
in ""lightweight_mutex::scoped_lock::scoped_lock"".
This behavior produced by error in
""boost::detail::allocator_impl"" or in Test Framework.
Mutex for locking created by static member. Automatic
unittests created by using global variables. So we have
using uninitialized CRITICAL_SECTION because order of
global variables initialization is undefined.

I tried to convert
""boost::detail::allocator_impl::mutex"" from static
variable to Meyer's singleton (with static member
function which contains local static variable ""mutex"").
This solves my problem but I can't suggest any patch
because I can't test it with many compilers.
}}}"	Bugs	closed		smart_ptr	None		Fixed