[pypy-issue] Issue #2579: pypy3.5 5.8.0 memory leak? (pypy/pypy)

strombrg issues-reply at bitbucket.org
Thu Jun 15 12:08:18 EDT 2017

New issue 2579: pypy3.5 5.8.0 memory leak?


I'm running http://stromberg.dnsalias.org/svn/backshift/trunk/ (that's an SVN URL) on a self-compiled pypy3.5 5.8.0.  This results in a very slow run, sluggishness in other applications on the same machine, and eventually the message "Killed" and a terminated pypy3.5.

I suspect this is a memory leak which is leading the Linux OOM Killer to kill the process.

The code runs fine on CPython 2.x, CPython 3.x, Jython and Pypy2. It used to run fine on Pypy3, but does no longer.

It's possible that the new lzma module is where the memory leak is.  The new lzma module is also the main reason I want to run the code on Pypy3.5.  Backshift uses lzma/xz heavily.

Sure enough, if I hack backshift to use ctypes and liblzma instead of the lzma module, I don't get a memory leak.

Any suggestions?


More information about the pypy-issue mailing list