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/+/7e7c04b677ebe6c6ed7caa359dfe34f13d2835e0 (Revert "[build] Make separate snapshot for trusted variant").

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.

PTAL Wasm folks. Looks like my CL was hiding this problem and it's revert revealed it again.

ClusterFuzz has detected this issue as fixed in range 52042:52043.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Ill
Crash Address: 0x5578d861326e
Crash State:
  v8::internal::CancelableTaskManager::Register
  Cancelable
  v8::internal::CancelableTask::CancelableTask
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=52028:52029
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=52042:52043

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

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

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