[Boost-users] Memory leak reported using threads library

From: gast128 (gast128_at_[hidden])
Date: 2004-11-22 17:21:03

Dear all,

Downloading and using the 1.32 version was probably not such a good idea... 

Now I get a mem-leak reported by the debug crt of VC 7.1. The report is 
located in 'init_threadmon_mutex' where a global object is allocated but never 
deleted. Before we start a discussion of what is a memory leak or not, in our 
production code we do not accept any leak reported by VC. The past has learned 
us that if you accept one leak, programmers/colleaques start to ignore them 
and in the end you have 200 leaks, instead of this one. 

I guess it wouldn't be difficult to resolve this one, on process exit it can 
be deallocated. And yes I am aware of the (phoenix) singleton discussions in 
Alexandrescu/Meyers, but really this kind of reinit of singletons after atexit 
calls won't happen too much.

Wkr, 
me