➜
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.
Created on 2011-03-05 00:10 by stutzbach, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| unicode-leak.patch | stutzbach, 2011-03-05 00:14 | |||
| Messages (2) | |||
|---|---|---|---|
| msg130090 - (view) | Author: Daniel Stutzbach (stutzbach)  |
Date: 2011-03-05 00:10 | |
By the time _PyUnicode_Init is called and does the following:
/* Init the implementation */
free_list = NULL;
numfree = 0;
free_list is already in use. _PyUnicode_Init clobbers whatever was stored there, leaking memory.
In Python 2, this was not an issue because no unicode functions were called prior to initialization. In Python 3, Unicode objects are created when initializing other types.
I found this using valgrind to search for "definitely lost" memory. I'd like to fix all of those cases, to make it easier to run valgrind on a regular basis.
I'll upload a patch momentarily.
|
|||
| msg133503 - (view) | Author: Stefan Krah (skrah) * |
Date: 2011-04-11 07:32 | |
This should be a duplicate of issue 10156. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:13 | admin | set | github: 55611 |
| 2011-04-11 07:32:27 | skrah | set | status: open -> closed superseder: Initialization of globals in unicodeobject.c nosy: + skrah messages: + msg133503 resolution: duplicate stage: patch review -> resolved |
| 2011-03-05 00:14:06 | stutzbach | set | keywords:
+ patch, needs review files: + unicode-leak.patch |
| 2011-03-05 00:10:48 | stutzbach | create | |