Message6017

Author zyasoft
Recipients adam.spiers, amak, colinhevans, fwierzbicki, matt_brinkley, pjenvey, zyasoft
Date 2010-08-25.06:18:50
SpamBayes Score 2.2998043e-08
Marked as misclassified No
Message-id <1282717131.67.0.769719302515.issue1327@psf.upfronthosting.co.za>
In-reply-to
Content
I've been thinking about this issue for a while, specifically the patch by Matt on July 7. The explicit clearing of all ThreadStates seems to me to be too drastic.

What I think we should do instead is associate a set of ThreadStstes with a given PySystemState (I don't believe one could share a TS across a PySystemState, and it certainly would not be advised.) When that PySystemState is being cleared, all the ThreadStates can then be released. This is also the appropriate time to run any Closer on opened files associated with the PySystemState. There may be other cleanup.

Any thoughts?

Lastly, I marked this issue urgent a couple of days ago because it's a bug that must be closed before we can do a 2.5.2 beta 2, given that it's a resource leak (especially given the type of apps this impacts).
History
Date User Action Args
2010-08-25 06:18:51zyasoftsetmessageid: <1282717131.67.0.769719302515.issue1327@psf.upfronthosting.co.za>
2010-08-25 06:18:51zyasoftsetrecipients: + zyasoft, fwierzbicki, amak, pjenvey, colinhevans, matt_brinkley, adam.spiers
2010-08-25 06:18:51zyasoftlinkissue1327 messages
2010-08-25 06:18:50zyasoftcreate