Opened 6 years ago
#12866 new Bugs
boost::interprocess::rbtree_best_fit::deallocate() throws boost::interprocess::lock_exception, although basic_managed_memory_impl::deallocate() docs says it never throws
| Reported by: | Owned by: | Ion Gaztañaga | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | interprocess |
| Version: | Boost 1.61.0 | Severity: | Problem |
| Keywords: | Cc: | alexryba@… |
Description
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?
Note:
See TracTickets
for help on using tickets.
