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/chromium/src/+/e206e5c21ee57618fc3c7fa9d59a60360d39f711 (Replace blink::ToIsolate(ExecutionContext) with blink::ExecutionContext->GetIsolate()).

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 614418:614419.

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

Fuzzer: inferno_webbot
Job Type: linux_ubsan_vptr_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000058
Crash State:
  blink::probe::AsyncTaskCanceledBreakable
  blink::DOMTimer::Stop
  blink::DOMTimerCoordinator::RemoveTimeoutByID
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=614196:614197
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=614418:614419

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

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

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