New submission from Antoine Pitrou <pit...@free.fr>: 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) ---------- files: memerr.py messages: 83292 nosy: amaury.forgeotdarc, pitrou priority: high severity: normal stage: needs patch status: open title: Singleton MemoryError can hold traceback data and locals indefinitely type: resource usage versions: Python 3.0, Python 3.1 Added file: http://bugs.python.org/file13261/memerr.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5437> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
