-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 20 October 2009, Nat Goodspeed wrote:
Would updating to Boost 1.40 solve this problem?
No
Or is there some explicit cleanup call we could/should make with a 1.39 boost::signals2::signal?
No. Even if there was, a signal invocation concurrent with the disconnect could keep the slot alive. So there would also need to to be a method which blocks until all currently in progress signal invocations complete (which might be useful to have anyways). Can you use a shared_ptr with a custom deleter to unload your dll an ensure it is not unloaded while it is still referenced? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkreHXwACgkQ5vihyNWuA4XiiQCghJPTWAZqGzRiCB45HFiN6DhC LWUAoNt8KPL+5XRpxlqs6MUlBlVebeu+ =QjUc -----END PGP SIGNATURE-----