-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential memory leak in Parser/parser.c #101046
Labels
type-bug
An unexpected behavior, bug, or error
Comments
pablogsal
added a commit
to pablogsal/cpython
that referenced
this issue
Jan 16, 2023
…n raising MemoryError
pablogsal
added a commit
that referenced
this issue
Jan 16, 2023
pablogsal
added a commit
to pablogsal/cpython
that referenced
this issue
Jan 16, 2023
…n raising MemoryError (pythonGH-101051). (cherry picked from commit 1de4395) Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
pablogsal
added a commit
to pablogsal/cpython
that referenced
this issue
Jan 16, 2023
…n raising MemoryError (pythonGH-101051). (cherry picked from commit 1de4395) Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
pablogsal
added a commit
that referenced
this issue
Jan 16, 2023
pablogsal
added a commit
that referenced
this issue
Jan 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
In
Parse/parse.c
, function_loop0_1_rule
(line 23809), object_children
If
PyMem_Realloc
fails, the original object will be kept untouched. Thus returning NULL without free'ing_children
will cause a memory leak.Your environment
Python 3.12
Linked PRs
The text was updated successfully, but these errors were encountered: