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/+/af677f29b1b7c0286b423c4e745303ed51de88e9 ([ic] EmitElementStore: don't miss when hitting new space limit.).

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 51305:51306.

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8_dbg
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0xffffffffffffffff
Crash State:
  v8::internal::ConsString::ConsStringVerify
  v8::internal::Object::ObjectVerify
  v8::internal::NewSpace::Verify
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=51296:51297
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=51305:51306

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

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