[issue41422] C Unpickler memory leak via memo

Change by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue41422] C Unpickler memory leak via memo

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 cell reference

[issue41422] C Unpickler memory leak via memo

Change by Roundup Robot : -- keywords: +patch nosy: +python-dev nosy_count: 1.0 -> 2.0 pull_requests: +20809 stage: -> patch review pull_request: https://github.com/python/cpython/pull/21664 ___ Python tracker _

[issue41422] C Unpickler memory leak via memo

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: kale-smo