Skip to content

Commit 6fd3c85

Browse files
bpo-36459: Fix a possible double PyMem_FREE() due to tokenizer.c's tok_nextc() (12601)
Remove the PyMem_FREE() call added in cb90c89. The buffer will be freed when PyTokenizer_Free() is called on the tokenizer state. (cherry picked from commit cda139d) Co-authored-by: Zackery Spytz <zspytz@gmail.com>
1 parent 3746635 commit 6fd3c85

File tree

2 files changed

+1
-1
lines changed

2 files changed

+1
-1
lines changed
Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
Fix a possible double ``PyMem_FREE()`` due to tokenizer.c's ``tok_nextc()``.

Parser/tokenizer.c

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1055,7 +1055,6 @@ tok_nextc(struct tok_state *tok)
10551055
newbuf = (char *)PyMem_REALLOC(newbuf,
10561056
newsize);
10571057
if (newbuf == NULL) {
1058-
PyMem_FREE(tok->buf);
10591058
tok->done = E_NOMEM;
10601059
tok->cur = tok->inp;
10611060
return EOF;

0 commit comments

Comments
 (0)