-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
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
Memory leak in AST parsing (OSS-Fuzz #60074) #106057
Comments
This doesn't seem to happen on the parser nor the tokenizer, so I am unasigning us from the issue. Os-fuzz detected that the bug was introduced in 04492cb so I am adding @markshannon to the issue |
If this is related to 04492cb why is the unparse/parse of bytes needed, or is that just as far as the fuzzer can simplify? |
Is there a way to see the original issue without a Google sign in? |
The fuzzer that found this bug is this, hence the reproducer is structured the same way.
I'm afraid not though it doesn't really contain any more information. |
That's helpful, thanks. |
Produces a different failure in debug build. Probably the same thing though: not handling recursion errors properly. |
Fixed by #106108 |
Bug report
Reported by OSS-Fuzz (issue 60074).
Build cpython with:
(Setting
ASAN_OPTIONS=detect_leaks=0
during build is necessary because memory leaks occur in the build phase itself, see #104791).Then run the following reproducer:
AddressSanitizer stack trace:
Bug was introduced in 04492cb @markshannon
Your environment
Linux x64, latest cpython main branch checkout.
Linked PRs
The text was updated successfully, but these errors were encountered: