Tim Peters wrote: > Because new-style classes create cycles that Py_Finalize() doesn't > clean up, it may make analysis easier to stick a PyGC_Collect() call > (or two! repeat until it returns 0) inside the loop now. I'm shy to do this: the comment in Py_Finalize suggests that things will break if there is a "late" garbage collection. > There is no way at present, short of editing the source for > Py_Finalize and recompiling. Presumably this is something that should > be addressed in the module initialization/finalization PEP, right? Indeed. >> This totals to 360, which is for some reason higher than the numbers >> I get when counting the objects on the global list of objects. > > How much higher? Well, I counted an increase of 156 objects on the "all objects" list, and an increase of 360 according to the COUNT_ALLOCS numbers. The first number was without COUNT_ALLOCS being defined, though. Anyway, thanks for your comments. I'll try to look at this from time to time, maybe I can resolve some of the leaks. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4