Re: [Boost-users] Memory leak reported using threads library

From: Cory Nelson (phrosty_at_[hidden])
Date: 2004-11-22 17:41:38

IIRC there was an intentional leak in the threads library that is
cleaned up on exit (the debug crt isn't perfect.. it can report global
std::strings as leaks also), maybe this is it?

On Mon, 22 Nov 2004 22:21:03 +0000 (UTC), gast128 <gast128_at_[hidden]> wrote:
> 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
> 
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users
> 

-- 
Cory Nelson
http://www.int64.org