Boost C++ Libraries: Ticket #8533: signal garbage collection of slot objects

version changed

julien.puydt@… — Fri, 27 Jun 2014 19:23:12 GMT

version Boost 1.52.0 → Boost 1.55.0

It's still the case with 1.55, and is annoying when one tries to reclaim memory as soon as possible and detect issues with memory management at fixed points.

Is there a workaround?

dsandras@… — Thu, 12 Feb 2015 09:02:50 GMT

We are really annoyed by this problem in the Ekiga project. What would you suggest ?

fmh6jj@… — Thu, 12 Feb 2015 16:29:10 GMT

I'll try to get this change done sometime in the next week

dsandras@… — Thu, 12 Feb 2015 16:34:09 GMT

Thanks !

What can we do to force the cleanup to happen until then?

Actually, when objects are destroyed when the process exits, we see all destructors are not called correctly because of this scheme.

fmh6jj@… — Thu, 12 Feb 2015 16:50:06 GMT

If you destroy a signal, all the slot objects it contains are also destroyed (unless it is concurrently being invoked when it is destructed, in which case the signal's internals are destructed when invocation completes).

status, milestone changed

Frank Mori Hess — Mon, 13 Apr 2015 01:47:22 GMT

status new → assigned
milestone To Be Determined → Boost 1.59.0

Fixed on develop branch

status changed; resolution set

Frank Mori Hess — Sat, 25 Apr 2015 17:15:52 GMT

status assigned → closed
resolution → fixed