➜

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 pitrou
Recipients amaury.forgeotdarc, pitrou
Date 2009-03-08.01:19:47
SpamBayes Score 0.00018627886
Marked as misclassified No
Message-id <1236475192.44.0.322213447469.issue5437@psf.upfronthosting.co.za>
In-reply-to
Content 
The PyExc_MemoryErrorInst object is persistent and its members never get
cleared. This means any local variable which gets caught in the
traceback isn't deallocated until the next MemoryError (!). Sample
script demonstrates this.

(this doesn't seem to affect 2.x because the traceback isn't attached to
the exception instance)
History
Date User Action Args
2009-03-08 01:19:53pitrousetrecipients: + pitrou, amaury.forgeotdarc
2009-03-08 01:19:52pitrousetmessageid: <1236475192.44.0.322213447469.issue5437@psf.upfronthosting.co.za>
2009-03-08 01:19:49pitroulinkissue5437 messages
2009-03-08 01:19:48pitroucreate