Re: Fwd: Re: 5.2 rc2 tarball now available

[Allin C. <cot...@wf...>]

On Thu, 6 Jul 2017, Ethan A Merritt wrote:

> I agree it is stupid that wxgtk does not perform its own initialization.
> But it doesn't.

Granted. However, the problem I've encountered lately is at the 
other end, wxt_atexit(), and specifically the call

thread->Wait()

in wxt_gui.cpp. This (but just sometimes, so maybe a race 
condition?) provokes in wxgtk 3 an assertion failure:

"./src/unix/threadpsx.cpp(1480): assert "This() != this" failed in 
Wait(): a thread can't wait for itself"

Is there perhaps a way to guard against that? I'm blissfully 
ignorant of C++ "this" shenanigans, but maybe something vaguely 
resembling

if (thread != this) // or This() ??
   thread->Wait();

Allin Cottrell