[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

Claudiu Popa added the comment: This was fixed a couple of months ago: https://hg.python.org/cpython/rev/07968254be96. Also, malloc was changed to PyMem_New a couple of weeks ago: https://hg.python.org/cpython/rev/036a2aceae93 -- nosy: +Claudiu.Popa resolution: -> fixed stage: needs p

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

Mark Lawrence added the comment: Can somebody answer the question about PyMem versus malloc/free functions. -- nosy: +BreamoreBoy ___ Python tracker ___ __

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

Changes by Brian Curtin : -- nosy: +brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue9191] winreg.c:Reg2Py() may leak memory (in unusual circumstances)

New submission from Daniel Stutzbach : In Reg2Py() in winreg.c, in the REG_MULTI_SZ case, there's the following: wchar_t **str = (wchar_t **)malloc(sizeof(wchar_t *)*s); if (str == NULL) return PyErr_NoMemory(); However, not all of the return