[Boost-bugs] [Boost C++ Libraries] #12866: boost::interprocess::rbtree_best_fit::deallocate() throws boost::interprocess::lock_exception, although basic_managed_memory_impl::deallocate() docs says it never throws

Subject: [Boost-bugs] [Boost C++ Libraries] #12866: boost::interprocess::rbtree_best_fit::deallocate() throws boost::interprocess::lock_exception, although basic_managed_memory_impl::deallocate() docs says it never throws
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2017-02-24 14:06:17

#12866: boost::interprocess::rbtree_best_fit::deallocate() throws
boost::interprocess::lock_exception, although
basic_managed_memory_impl::deallocate() docs says it never throws
---------------------------------------------+--------------------------
 Reporter:  Alexey Rybalchenko <alexryba@…>  |      Owner:  igaztanaga
     Type:  Bugs                             |     Status:  new
Milestone:  To Be Determined                 |  Component:  interprocess
  Version:  Boost 1.61.0                     |   Severity:  Problem
 Keywords:                                   |
---------------------------------------------+--------------------------
 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?

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