[Lazarus] Lazarus application crash. Is PostMessage thread safe?

[Michael Schnell]

On 02/15/2016 07:23 PM, Giuliano Colla wrote:
>
>>
>>>
>>> The result is to make Application.ProcessMessage not 100% reentrant, 
>>> because of a Glib2 bug.
>> Would you suggest not to handle "the same" event ? How should you 
>> detect that its the event already in the works or the next occurrence  ?
>>
> In the case I've stumbled into, when next message eventually comes 
> (after 1722 iterations over the previous one) the program crashes for 
> a  SEGFAULT, most likely generated by a stack overflow.
Anyway, IMHO it's not a good idea to fight a (potential) bug (in "Glib2" 
whatever this exactly means) by implementing a completely queer behavior 
in Application.ProcessMessage.

-Michael