Message 323506 - Python tracker

➜

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	sir-sigurd
Recipients	pablogsal, sir-sigurd
Date	2018-08-14.10:10:26
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
> Could you elaborate a bit more on how/where the leak happens? It happens when PyMem_Resize() fails. It was used like this: Py_UCS4 *field = self->field; self->field = PyMem_Resize(field, Py_UCS4, self->field_size); The last statement changes both self->field and field (macro magic!), so in the case PyMem_Resize() fails, previously allocated memory can't be freed.

> Could you elaborate a bit more on how/where the leak happens?

It happens when PyMem_Resize() fails. It was used like this:

Py_UCS4 *field = self->field;
self->field = PyMem_Resize(field, Py_UCS4, self->field_size);

The last statement changes both self->field and field (macro magic!), so in the case PyMem_Resize() fails, previously allocated memory can't be freed.

History
Date	User	Action	Args
2018-08-14 10:10:26	sir-sigurd	set	recipients: + sir-sigurd, pablogsal
2018-08-14 10:10:26	sir-sigurd	set	messageid: <[email protected]>
2018-08-14 10:10:26	sir-sigurd	link	issue34395 messages
2018-08-14 10:10:26	sir-sigurd	create