id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
12866	boost::interprocess::rbtree_best_fit::deallocate() throws boost::interprocess::lock_exception, although basic_managed_memory_impl::deallocate() docs says it never throws	Alexey Rybalchenko <alexryba@…>	Ion Gaztañaga	"Hi,

I am using boost interprocess 1.61.
The destructor of one of my classes calls:
boost::interprocess::managed_shared_memory::deallocate(ptr);

As far as I can tell from the docs of basic_managed_memory_impl::deallocate(), it shouldn't throw. But the rbtree_best_fit::deallocate() throws an boost::interprocess::lock_exception.

Is it a bug, or am I missing something? Should I not call deallocate from a destructor?"	Bugs	new	To Be Determined	interprocess	Boost 1.61.0	Problem			alexryba@…