<story><title>Tracking Down a Python Memory Leak</title><url>https://benbernardblog.com/tracking-down-a-freaky-python-memory-leak/</url></story><parent_chain></parent_chain><comment><author>guyzero</author><text>&amp;quot;What&amp;#x27;s possible, though, is accumulating Python objects in memory and keeping strong references to them12. For instance, this happens when we build a cache (for example, a dict) that we never clear. The cache will hold references to every single item and the GC will never be able to destroy them, that is, unless the cache goes out of scope.&amp;quot;&lt;p&gt;Back when I worked with a Java memory profiling tool (JProbe!) we called these &amp;quot;lingerers&amp;quot;. Not leaks, but the behaviour was similar.</text></comment>
<story><title>Tracking Down a Python Memory Leak</title><url>https://benbernardblog.com/tracking-down-a-freaky-python-memory-leak/</url></story><parent_chain></parent_chain><comment><author>tantalor</author><text>Spoiler alert, the leak is in libxml2, not Python code.</text></comment>