Boost C++ Libraries: Ticket #2991: Broadcast of bool leaks memory

attachment set

micdestefano@… — Tue, 05 May 2009 08:12:58 GMT

attachment → bool_bcast.cpp

Test program that demonstrates the bug and its possible solution

status, version, severity changed; resolution set

Matthias Troyer — Tue, 05 May 2009 16:36:17 GMT

status new → closed
version Boost 1.38.0 → Boost Development Trunk
resolution → duplicate
severity Problem → Cosmetic

This is a duplicate of #2594. It is a cosmetic issue that comes up with valgrind but has no other impact.

status changed; resolution deleted

anonymous — Wed, 06 May 2009 05:59:42 GMT

status closed → reopened
resolution duplicate

Replying to troyer:

This is a duplicate of #2594. It is a cosmetic issue that comes up with valgrind but has no other impact.

Excuse me, but ticket #2594 shows something totally different ... please, read carefully my comments for that ticket (the problem for that ticket is absolutely not cosmetic and this ticket is not a duplicate of that one ... for ticket #2594, if you don't fix the bug the code does not get built at all, because you receive an error from the compiler).

For this ticket, I repeat, if you free the new data type, no leak is generated (please, look at the example code I sent). I don't think this is cosmetic: who does free the new data type if you never call MPI_Type_free ?

status changed; resolution set

anonymous — Wed, 06 May 2009 06:57:57 GMT

status reopened → closed
resolution → duplicate

Sorry, I meant 2586. This is cosmetic since the memory would be released by a destructor call of a static member variable. This destructor would only called at the end of the program execution anyway, and the leak thus has no effect besides being detected by valgrind. Hence I call it cosmetic.

anonymous — Wed, 06 May 2009 07:31:28 GMT

Replying to anonymous:

Sorry, I meant 2586. This is cosmetic since the memory would be released by a destructor call of a static member variable. This destructor would only called at the end of the program execution anyway, and the leak thus has no effect besides being detected by valgrind. Hence I call it cosmetic.

Ok. Clear.
Thank you very much.