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/+/d42534d441a75405d8dcf50a1383485b3c135faf (Remove always-on flags for RegExp dotAll and lookbehind).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

This crash is in code-zapping, doesn't look related to my change. Ulan, can you triage for GC?

This sounds very similar to  issue v8:7100 , though I don't see --write-protect-code-pages passed to this test.

It is passing --future, which implies --write-protect-code-memory, so pretty sure it's the same.

ClusterFuzz has detected this issue as fixed in range 49520:49521.

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8_dbg
Platform Id: windows

Crash Type: UNKNOWN WRITE
Crash Address: 0x250067a0
Crash State:
  v8::internal::FreeList::Allocate
  v8::internal::PagedSpace::AllocateRawUnaligned
  v8::internal::Heap::AllocateRaw
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=49452:49453
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=49520:49521

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

See https://github.com/google/clusterfuzz-tools 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