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=5663321882361856

Fuzzer: decoder_langfuzz
Job Type: linux_msan_d8
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x000300000007
Crash State:
  v8::internal::HeapObject::SizeFromMap
  v8::internal::MarkCompactCollector::ProcessMarkingWorklist
  v8::internal::MarkCompactCollector::MarkLiveObjects
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

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

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

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