Michael Pfeiffer wrote: > BTW who has added the delete statement and the comment in > PairsWindow::MessageReceived()? > > delete fPairComparing; > // message of message runner might not have arrived // yet, so it > is deleted here to prevent any leaking // just in case > > When that code path is reached it can be asserted that fPairComparing is > always NULL. I did, and also added the comment. I might be missing something, but why is it not possible to click onto another button quickly enough, before the message from the old message runner arrives? Best regards, -Stephan