New submission from Daniel Stutzbach <[email protected]>:
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 paths after that point call free(str).
The leaking paths are pretty unusual, so I'm setting the priority to low. The
leaking paths occur when PyList_New returns NULL or if the registry entry
contains more than INT_MAX characters.
Two other things I noticed and I'm not sure about:
Is INT_MAX really the maximum number of characters for a Python unicode string?
Should this be using PyMem functions instead of malloc/free?
----------
assignee: stutzbach
components: Windows
messages: 109486
nosy: stutzbach
priority: low
severity: normal
stage: needs patch
status: open
title: winreg.c:Reg2Py() may leak memory (in unusual circumstances)
type: resource usage
versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue9191>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
