Message 149895 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jcea
Recipients	David.Butler, amaury.forgeotdarc, jcea
Date	2011-12-20.00:23:27
SpamBayes Score	5.7323105e-05
Marked as misclassified	No
Message-id	<1324340608.75.0.969472117779.issue13616@psf.upfronthosting.co.za>
In-reply-to

Content
It seems to be a real infinite loop. Bad thing. Could be a bug in an extension, difficult to say. This is going to be VERY difficult to debug without a reproductible case we can try. Could you possibly check the object type of the "infinite loop" object?. If the loop is from an object to itself, maybe you can instrumentalize python to detect this loop when created. Add to your code "gc.collect()" is a frequent loop. It is going to suck CPU, but could reproduce the issue faster and make it easier to diagnose.

It seems to be a real infinite loop. Bad thing. Could be a bug in an extension, difficult to say.

This is going to be VERY difficult to debug without a reproductible case we can try.

Could you possibly check the object type of the "infinite loop" object?. If the loop is from an object to itself, maybe you can instrumentalize python to detect this loop when created.

Add to your code "gc.collect()" is a frequent loop. It is going to suck CPU, but could reproduce the issue faster and make it easier to diagnose.

History
Date	User	Action	Args
2011-12-20 00:23:28	jcea	set	recipients: + jcea, amaury.forgeotdarc, David.Butler
2011-12-20 00:23:28	jcea	set	messageid: <1324340608.75.0.969472117779.issue13616@psf.upfronthosting.co.za>
2011-12-20 00:23:28	jcea	link	issue13616 messages
2011-12-20 00:23:27	jcea	create