Hi Jim, On 2 August 2015 at 08:57, jim horng <jimho...@gmail.com> wrote: > I didn't state clear that I already tried periodic gc but memory usage still > increase over team till out of memory, so we assume it's a real leak cause > by python program but we don't have good tool/methodology to hunt it, thanks > :)
I believe you are failing to understand Phyo's answer: PyPy 2.3.1 had some internal memory leaks that were fixed later. If you're running into these, there is nothing you can do but upgrade to a more recent PyPy. There are no Python-level tricks that can free this leaked memory. A bientôt, Armin. _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
