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/+/12420537c8e4f391b010950f154be3ad3a2a080e ([heap] fix Sweeper::kNumberOfSweepingSpaces).

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.

Fixed by https://chromium-review.googlesource.com/c/v8/v8/+/992152

ClusterFuzz has detected this issue as fixed in range 52322:52323.

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

Fuzzer: decoder_langfuzz
Job Type: linux_msan_d8
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  v8::internal::Sweeper::PauseOrCompleteScope::PauseOrCompleteScope
  v8::internal::Heap::Scavenge
  v8::internal::Heap::PerformGarbageCollection
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_d8&range=52319:52320
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_d8&range=52322:52323

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

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 5461822979964928 is verified as fixed, so closing issue as verified.

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

Also found by internal fuzzers, I'm afraid.

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