On Mon, 18 Dec 2023 19:15:03 GMT, Martin Fox wrote:
>> While processing a key down event the Glass GTK code sends out PRESSED and
>> TYPED KeyEvents back to back. If the stage is closed during the PRESSED
>> event the code will end up referencing freed memory while sending out the
>> TYPED
On Mon, 18 Dec 2023 19:15:03 GMT, Martin Fox wrote:
>> While processing a key down event the Glass GTK code sends out PRESSED and
>> TYPED KeyEvents back to back. If the stage is closed during the PRESSED
>> event the code will end up referencing freed memory while sending out the
>> TYPED
On Mon, 18 Dec 2023 19:15:03 GMT, Martin Fox wrote:
>> While processing a key down event the Glass GTK code sends out PRESSED and
>> TYPED KeyEvents back to back. If the stage is closed during the PRESSED
>> event the code will end up referencing freed memory while sending out the
>> TYPED
On Mon, 18 Dec 2023 19:15:03 GMT, Martin Fox wrote:
>> While processing a key down event the Glass GTK code sends out PRESSED and
>> TYPED KeyEvents back to back. If the stage is closed during the PRESSED
>> event the code will end up referencing freed memory while sending out the
>> TYPED
> While processing a key down event the Glass GTK code sends out PRESSED and
> TYPED KeyEvents back to back. If the stage is closed during the PRESSED event
> the code will end up referencing freed memory while sending out the TYPED
> event. This can lead to intermittent crashes.
>
> In
On Mon, 18 Dec 2023 19:15:03 GMT, Martin Fox wrote:
>> While processing a key down event the Glass GTK code sends out PRESSED and
>> TYPED KeyEvents back to back. If the stage is closed during the PRESSED
>> event the code will end up referencing freed memory while sending out the
>> TYPED
