Object destruction and cross thread signal activation

[coolcode123]

I think I've found a serious bug in CsSignal. I had several program crashes before I figured out what was going on.
If we have two objects assigned to two different threads (so these two threads decide when to destroy those objects), and one object gets destroyed by its associated thread while another object emits a signal, this line of code will crash the entire program:

cs_signal/src/cs_signal.h

Line 183 in f20001a

bool receiverInSameThread = receiver->compareThreads();

The problem here is the following: the receiver is half-destroyed and it didn't have any chance to disconnect itself in its own thread (base destructor runs last), but another thread !synchronously! tests the receiver's thread affinity and then even calls receiver->queueSlot() on that half-destroyed object.
This makes the entire activate() method not thread safe.

[agserm]

Thanks for reporting this, it sounds like you have done a lot of work to track this down. We will investigate and start looking at how to address this issue.