BTW, Nick Coghlan said:

>The most likely culprit is that some of the code is using PyMem_Free on
>a pointer allocated with PyObject_Malloc (or vice-versa). This has
>always been illegal, but prior to 2.5 the Python memory allocator tied
>itself in knots to try to avoid crashing when client code broke the
>rules. The changes in 2.5 to release unused memory back to the OS
>required that those knots be cut.

>The what's new document for each release is a good resource for these
>kinds of problems, especially its porting section:


Which looks to me to be the most likely case, but I find the majority
of the PyGEGL code inscrutable.
Gimp-developer mailing list

Reply via email to