-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday 29 September 2010, Denis Arnaud wrote:
2010/8/27 Denis Arnaud <denis.arnaud_boost@m4x.org>
Hello,
a Fedora user has reported a potential memory leak in Boost.Thread (see https://bugzilla.redhat.com/show_bug.cgi?id=627875 for details), detected with Valgrind in (at least) versions 1.41.0 and 1.44.0.
Apparently, as per https://bugzilla.redhat.com/show_bug.cgi?id=627875#c7 , it seems there is a bug in Boost Thread.
As I'm not a specialist in that area, I prefer to hand it over to more savvy developers on the list. Do not hesitate to answer directly on Bugzilla.
As far as I can tell, the "fix" for this "bug" is to insure some per-thread memory is freed just before the entire program exits? The only point to doing that would be to quiet valgrind. Maybe the reason posix threads don't invoke their per-thread data destructors is that it is pointless? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkyjkNUACgkQ5vihyNWuA4UqbwCeP9SYukja0bDnp0txFRgHfJ0a sxIAoMmO4Fw+0T13v/0QPVWFAt+kuxXB =VDET -----END PGP SIGNATURE-----