RetroSearch Browse

Mon Nov 21 16:57:05 EST 2016 · https://mail.python.org/pipermail/python-dev/2016-November/146845.html

On 2016-11-19 2:46 PM, Kevin Modzelewski wrote:
> Hi Yury, you may be interested in some leak-finding code that wrote for
> Pyston.  It uses the GC infrastructure to show you objects that were
> directly leaked, ignoring indirect leaks -- ie objects that were only
> leaked because they were referenced by a leaked object.  It can often give
> you a very small list of objects to look into (depending on how many non-gc
> objects were leaked).  If you're interested I can try porting it to CPython.
>
> https://github.com/dropbox/pyston/blob/master/from_cpython/Modules/gcmodule.c#L894

Hi Kevin,

Nice work! Anything to help to find refleaks is welcome, it's really a 
painful process sometimes.  As for porting it to CPython - I don't see 
why not.  We can add this new API to debug builds only, at least in the 
beginning.

Thank you!
Yury

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2016-November/146845.html below:

[Python-Dev] [Python-checkins] Daily reference leaks (b78574cb00ab): sum=1120