Repository navigation
Memory leak in AST parsing (OSS-Fuzz #60074) #106057
Description
Activity
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on Jun 24, 2023 - addedperformancePerformance or resource usagePerformance or resource usageinterpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)3.13only security fixesonly security fixes
on Jun 24, 2023 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
Reacted by Lysandros NikolaouIf 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?
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?
The fuzzer that found this bug is this, hence the reproducer is structured the same way.
Is there a way to see the original issue without a Google sign in?
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.
- added a commit that references this issue
on Jul 7, 2023 Fixed by #106108
Bug report
Reported by OSS-Fuzz (issue 60074).
Build cpython with:
(Setting
ASAN_OPTIONS=detect_leaks=0during 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