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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/d7fda25256fd3e1e37191eaf17080b447e708993 ([ignition] Move suspend_id assignment to bytecode generation).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

ClusterFuzz has detected this issue as fixed in range 532428:532438.

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

Fuzzer: libFuzzer_v8_regexp_builtins_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  !spread_pos.IsValid() in parser-base.h
  v8::internal::ParserBase<v8::internal::PreParser>::ParseV8Intrinsic
  v8::internal::ParserBase<v8::internal::PreParser>::ParsePrimaryExpression
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=531461:531791
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=532428:532438

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

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.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot