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 yselivanov
Recipients Elvis.Pranskevichus, Mark.Shannon, pablogsal, vstinner, yselivanov
Date 2022-01-11.21:06:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1641935170.22.0.878820300431.issue46347@roundup.psfhosted.org>
In-reply-to
Content
I'm investigating a memory leak in 3.10, and while looking at the offending commit I stumbled upon this: in ceval.c:PyEval_EvalCodeEx, there's this allocation:

    PyObject **kwargs = PyMem_Malloc(sizeof(PyObject *)*kwcount);

The problem is that this isn't ever freed. And `kwargs` isn't used anywhere in the function body. It seems to me that this is silently leaking memory.
History
Date User Action Args
2022-01-11 21:06:10yselivanovsetrecipients: + yselivanov, vstinner, Elvis.Pranskevichus, Mark.Shannon, pablogsal
2022-01-11 21:06:10yselivanovsetmessageid: <1641935170.22.0.878820300431.issue46347@roundup.psfhosted.org>
2022-01-11 21:06:10yselivanovlinkissue46347 messages
2022-01-11 21:06:10yselivanovcreate