[issue23782] Leak in _PyTraceback_Add

Changes by Donald Stufft : -- pull_requests: +951 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue23782] Leak in _PyTraceback_Add

Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7 ___ Python tracker ___ ___

[issue23782] Leak in _PyTraceback_Add

Roundup Robot added the comment: New changeset 6b3be9f38f2a by Serhiy Storchaka in branch '3.5': Issue #23782: Fixed possible memory leak in _PyTraceback_Add() and exception https://hg.python.org/cpython/rev/6b3be9f38f2a New changeset 2d352bf2b228 by Serhiy Storchaka in branch '3.6': Issue #2378

[issue23782] Leak in _PyTraceback_Add

Serhiy Storchaka added the comment: More refactoring. -- Added file: http://bugs.python.org/file45036/_PyTraceback_Add_leak2.patch ___ Python tracker ___

[issue23782] Leak in _PyTraceback_Add

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23782] Leak in _PyTraceback_Add

Serhiy Storchaka added the comment: Proposed patch fixes a leak. -- components: +Interpreter Core keywords: +patch stage: -> patch review versions: +Python 3.5, Python 3.6 Added file: http://bugs.python.org/file43473/_PyTraceback_Add_leak.patch ___ P

[issue23782] Leak in _PyTraceback_Add

STINNER Victor added the comment: If a new exception is raised by _PyTraceback_Add(), the original exception is lost. It's sad because _PyTraceback_Add() is supposed to enhance the current exception, not to drop it. In the draft of my PEP 490, I propose to chain the two exceptions. --

[issue23782] Leak in _PyTraceback_Add

New submission from Serhiy Storchaka: There is a leak of fetched exception in _PyTraceback_Add() (Python/traceback.c:146). -- messages: 239319 nosy: georg.brandl, haypo, serhiy.storchaka priority: normal severity: normal status: open title: Leak in _PyTraceback_Add type: resource usage