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/+/2363cdfefeb643285cbe8593b7c17d80e5d06cd9 ([tracing] do not add traces when disabled).

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.

Similar to https://bugs.chromium.org/p/chromium/issues/detail?id=883181, I don't see how my CL could have caused this. Perhaps there is some flakiness? Unassigning to get this re-triaged.

ClusterFuzz has detected this issue as fixed in range 55818:55819.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_ubsan_vptr_d8
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x00000000007c
Crash State:
  NeedsContext
  v8::internal::Scope::ContextChainLength
  ContextChainDepth
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=55808:55809
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_d8&range=55818:55819

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

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

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