Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Unable to find actual suspect through code search nor from the provided regression range. This issue looks similar to  Issue 806620   , hence assigning it to the concern owner for further inputs.

joelhockey@-- Could you please take a look into this issue?

Thanks!

Sorry, I'm not working on libxml now.

ClusterFuzz has detected this issue as fixed in range 574139:574142.

Detailed report: https://clusterfuzz.com/testcase?key=5287165811228672

Fuzzer: libFuzzer_gn_parser_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffe7618f948
Crash State:
  Parser::ParseExpression
  Parser::DotOperator
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=474915:474952
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=574139:574142

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5287165811228672

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 5287165811228672 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.