[issue39061] Garbage Collection optimizations cause "memory leak"

Maxime Istasse added the comment: > The fact that the GC will take longer time does not qualify this as memory > leaks. A memory leak is by definition memory that cannot be reclaimed and in > this case, once the collection of the old generation happens it will be > collected, therefore is no

[issue39061] Garbage Collection optimizations cause "memory leak"

Pablo Galindo Salgado added the comment: > It happens to cause huge memory leaks if the self-referencing objects > occupies a lot of RAM, which should be expected. The fact that the GC will take longer time does not qualify this as memory leaks. A memory leak is by definition memory that can

[issue39061] Garbage Collection optimizations cause "memory leak"

Change by Karthikeyan Singaravelan : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue39061] Garbage Collection optimizations cause "memory leak"

Maxime Istasse added the comment: TLDR; a short-lived object can make it directly from young generation to old generation if middle generation collection kicks in while it is not freeable yet. Old generation is very rarely collected. Several of those objects, if they imply cyclic references,

[issue39061] Garbage Collection optimizations cause "memory leak"

New submission from Maxime Istasse : When working on a self-referencing object in the young generation and the middle-generation collection kicks in, that object is directly moved to the old generation. (if I understood this well: https://github.com/python/cpython/blob/d68b592dd67cb87c4fa862a