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/+/e9750cb80653827a0c685fe65b9572315fe1d4e4 (Preempt ConcurrentMarking tasks instead of merely pausing in PauseScope.).

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 51362:51363.

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

Fuzzer: v8_builtins_generator
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x37e71ec02200
Crash State:
  v8::internal::ConcurrentMarking::Run
  v8::platform::WorkerThread::Run
  v8::base::ThreadEntry
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=51355:51356
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=51362:51363

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

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

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

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