[Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494 (original) (raw)
Brett Cannon brett at python.org
Wed Oct 21 12:58:22 EDT 2015
- Previous message (by thread): [Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494
- Next message (by thread): [Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 21 Oct 2015 at 09:33 Joe Jevnik <jjevnik at quantopian.com> wrote:
Sorry about introducing this. Where can I subscribe to these automated emails.
The emails are sent to the python-checkins mailing list.
Also, how do I go about running this locally?
If you look at the bottom of the email that reports the leaks you will notice it tells you how the tests were run, e.g.:
['./python', '-m', 'test.regrtest', '-uall', '-R', '3:3:/home/psf-users/antoine/refleaks/reflogyrNnBL', '--timeout', '7200']
-Brett
On default I tried running
./python -m test -l testcapi
did not print anything about leaks. I think that usingobject._new_
as a decorator here is the same as subclassing object, overriding new and then making a call tosuper()._new_
so I would imagine this bug could appear in less "clever" situations. I would love to help fix this issue; Benjamin, you mentioned that you think that maybe all heaptypes should have gc, do you have a suggestion on where I can look in the code to try to make this change?On Wed, Oct 21, 2015 at 11:53 AM, Random832 <random832 at fastmail.com> wrote:
Raymond Hettinger <raymond.hettinger at gmail.com> writes: > Thanks for hunting this down. I had seen the automated reference leak > posts but didn't suspect that a pure python class would have caused > the leak. > > I'm re-opening > https://mail.python.org/pipermail/python-dev/2015-October/141993.html > and will take a look at it this weekend. If I don't see an obvious > fix, I'll revert Joe's patch until a correct patch is supplied and > reviewed.
If a pure python class can cause a reference leak, doesn't that mean it is only a symptom rather than the real cause? Or is it that the use of @object.new is considered "too clever" to be worth fixing?
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/joe%40quantopian.com
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20151021/9dfb22c9/attachment.html>
- Previous message (by thread): [Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494
- Next message (by thread): [Python-Dev] [Python-checkins] Daily reference leaks (d7e490db8d54): sum=61494
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]