I don't know how valid is that nowadays; but I recovered it recently - and it is a clear-cut stacktrace.
May still be valid.
There was a tiny race condition, fixed in r26032, but I doubt that you were hitting this very unlikely race, I think it is more likely that the interpreter is in the process of shutting down following the control-C
and so random object can get nullified.
I'm not going to worry about this one unless it can be reproduced more reliably.
Xpra GTK3 client version 3.0-r23250 64-bit
That's pretty old! 3.0!
Replying to Antoine Martin:
Xpra GTK3 client version 3.0-r23250 64-bit
That's pretty old! 3.0!
As I said
I don't know how valid is that nowadays; but I recovered it recently - and it is a clear-cut stacktrace.
I have stored this stacktrace somewhere to report it sometime, but it kinda fell through the tracks.
I will be on the lookout (as always) if anything comes to the console
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2716