Boost logo

Boost Users :

Subject: Re: [Boost-users] Memory management of boost::mutex
From: Markus Henschel (markus.henschel_at_[hidden])
Date: 2010-07-13 04:52:46

> -----Ursprüngliche Nachricht-----
> Von: boost-users-bounces_at_[hidden] [mailto:boost-users-
> bounces_at_[hidden]] Im Auftrag von Anthony Williams
> Gesendet: Montag, 12. Juli 2010 19:08
> An: boost-users_at_[hidden]
> Betreff: Re: [Boost-users] Memory management of boost::mutex
> Markus Henschel <markus.henschel_at_[hidden]> writes:
> > we have a custom memory manager that overrides global new/delete. It
> > is currently not thread safe. Because we require thread safety now I
> > wanted to ad a mutex and some locks around the critical
> > parts. Unfortunately boost::mutex allocates memory itself.
> boost::mutex does not directly allocate any memory itself, so this
> should not be a problem. Which version of boost are you using, on which
> platform?
> Anthony
> --
> Author of C++ Concurrency in Action
> just::thread C++0x thread library
> Just Software Solutions Ltd
> 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No.
> 5478976
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]

Currently we use 1.34.1 but will soon upgrade to 1.43.0. At least in 1.34.1 when BOOST_HAS_WINTHREADS is defined a mutex allocates memory for a win32 CRITICAL_SECTION using new operator. It seems like the implementation in 1.43.0 has changed completely. Would be great if there was no more dynamic memory allocation. On the other hand I can never be sure if boost mutex will change the implementation again in future versions. Mmmmmm...

Boost-users list run by williamkempf at, kalb at, bjorn.karlsson at, gregod at, wekempf at