bpo-36459: Fix a possible double PyMem_FREE() due to tokenizer.c's to…

…k_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 <[email protected]>
ActiveState · Mar 28, 2019 · dffe90e · dffe90e
1 parent bb89aa2
commit dffe90e
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 1 deletion.
diff --git a/Misc/NEWS.d/next/Core and Builtins/2019-03-27-22-35-16.bpo-36459.UAvkKp.rst b/Misc/NEWS.d/next/Core and Builtins/2019-03-27-22-35-16.bpo-36459.UAvkKp.rst
@@ -0,0 +1 @@
+Fix a possible double ``PyMem_FREE()`` due to tokenizer.c's ``tok_nextc()``.
diff --git a/Parser/tokenizer.c b/Parser/tokenizer.c
@@ -979,7 +979,6 @@ tok_nextc(register struct tok_state *tok)
                 newbuf = (char *)PyMem_REALLOC(newbuf,
                                                newsize);
                 if (newbuf == NULL) {
-                    PyMem_FREE(tok->buf);
                     tok->done = E_NOMEM;
                     tok->cur = tok->inp;
                     return EOF;
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		Fix a possible double ``PyMem_FREE()`` due to tokenizer.c's ``tok_nextc()``.