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/+/77b0baa6494d528a6b892160703edb087473efcd ([wasm] Fix importing wasm-lazy-compile stubs).

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

This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Bisects to f139f17e59b2fcdf8496e95058d68f7879b2c502 (Stage write-protected code behind the --future flag.).
You might have to try different gc-intervals to reproduce.

Lowering priority, as this is behind the --future flag.

ClusterFuzz has detected this issue as fixed in range 49532:49533.

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

Fuzzer: mbarbella_js_mutation
Job Type: mac_asan_d8_dbg
Platform Id: mac

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  write_unprotect_counter_ <= 3 in spaces.cc
  v8::internal::MemoryChunk::SetReadAndWritable
  CodePageMemoryModificationScope
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_d8_dbg&range=49404:49405
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_d8_dbg&range=49532:49533

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

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.

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

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