On Fri, 8 Jul 2022 at 07:48, Jck_01 wrote:
>
>> That sounds most curious - if the async call is not interacting with fltk at all, I’d expect it to be “safe”, so this is unexpected. Does it (the async method) interact with the GUI context in some way, or something?
>
>
> As far as I know - it doesn't at all.
>

OK... well, that was my best guess, so I'm at something of a loss as
to what to try next!

It is increasingly looking like some sort of dangling pointer issue,
as Albrecht (and others) have suggested.
Which might be a hard thing to debug...

-- 
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/CAGFM6dZaXqjwT2fsRnUMw-zXJ7Ss%3Dp9zgUu0ksU6vnuqFzM-0A%40mail.gmail.com.