Hi Johannes, i would have been surprised if FLEXT_NOGLOBALNEW would have helped. In any case, i'm trying to track down the issue... it seems to be present in linux only. I hope valgrind can help me to find it shortly.
best greetings, Thomas
a quick solution would be to define FLEXT_NOGLOBALNEW when compiling your flext externals.
I tried that, but pd still exits with the "double free" message, and sometimes (ie in a large patch with loads of xrecords and pools), segfaults when closing a patch. I will look a bit more into it later, to see if i've overlooked something... but if anyone has some, i'm open for suggestions.
thanks, Johannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list