New submission from kale-smoothie :
Unless I've misread or misunderstood, the documentation at
https://docs.python.org/3/reference/import.html#loaders for the deprecated
`load_module` method doesn't indicate any requirements or caveats for thread
safe importing. As it stands, I t
kale-smoothie added the comment:
The leak demonstrated in the attachment is, to my understanding, caused by
memoizing the closure returned from the `find_class` method that's used to
intercept global references. The cycle is then: Unpickler, memo table, closure,
Unpickler (via
New submission from kale-smoothie :
I'm not familiar with the workings of GC/pickle, but it looks like the traverse
code in the C Unpickler omits a visit to the memo, potentially causing a memory
leak?
--
components: Library (Lib)
files: leak_pickler.py
messages: 374518
nosy:
