Re: [Pyfltk-user] Mystery swig error when exiting pyfltk program

[Andreas H. <and...@bl...>]

Hi Dima and Robert

I can also reproduce the problem here. All I can say at the moment is 
that it happens in the function  SwigPyObject_dealloc and that it seems 
to be a kind of race condition. It could well be related to the previous 
issue mentioned by Dima, however, I do get somehow a slightly different 
feeling.

First of all, what is the intention of calling window.end() before 
window.show()? Is this just something you tried or is there a deeper use 
case to it?

Unfortunately, I will now be away for two weeks without access to my 
computer, but I will join in again once I am back.

Best egads

Andreas

On 6/27/25 19:59, Dima Kogan wrote:
> Hi. Thanks for looking. I just dug into it a bit also, and it started to
> look familiar. We already looked into this sort of thing here:
>
>    https://sourceforge.net/p/pyfltk/mailman/pyfltk-user/thread/1014543129.14367.1712509274536%40bluewin.ch/#msg58757564
>
> The punchline is that swig has a bug: it should do most of its
> deallocation in tp_finalize, but instead it puts everything into
> tp_destroy. This makes it possible for stuff to be cleaned-up out of
> order. In THIS case it looks like the derived Fl_Window type in
> Fl_Gl_Image_Widget is being cleaned up twice, or something of that
> nature. I don't know if this swig problem is THE problem here, but it's
> adjacent. Did either of you happen to talk to the swig folks about it
> the last time around?
>
> Thanks
>
>
> _______________________________________________
> Pyfltk-user mailing list
> Pyf...@li...
> https://lists.sourceforge.net/lists/listinfo/pyfltk-user