Message 269885 - 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	aonishuk
Recipients	aonishuk, gps, gregory.p.smith, ppperry, r.david.murray
Date	2016-07-06.13:56:18
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1467813379.06.0.927536624623.issue27448@psf.upfronthosting.co.za>
In-reply-to

Content
Gregory P. Smith, "if you are seeing a memory leak and the statements that fail before the gc.enable call are more than" The problem in my case was different. It was race condition between gc.isenabled and gc.disable. Isenabled was called when gc was disabled by another subprocess. This caused that later on gc.enable was not triggered.

Gregory P. Smith, 

"if you are seeing a memory leak and the statements that fail before the gc.enable call are more than"

The problem in my case was different. It was race condition between gc.isenabled and gc.disable. 

Isenabled was called when gc was disabled by another subprocess. This caused that later on gc.enable was not triggered.

History
Date	User	Action	Args
2016-07-06 13:56:19	aonishuk	set	recipients: + aonishuk, gregory.p.smith, gps, r.david.murray, ppperry
2016-07-06 13:56:19	aonishuk	set	messageid: <1467813379.06.0.927536624623.issue27448@psf.upfronthosting.co.za>
2016-07-06 13:56:19	aonishuk	link	issue27448 messages
2016-07-06 13:56:18	aonishuk	create