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/+/391a1ccc52ae5b110b841b3ac428103087414dbb (Fixing oauth token for histogram upload).

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.

That's a bogus clusterfuzz blame. But the Skia roll might be the cause. Over to canvas for triage, as I have no idea what is supposed to happen here.

ClusterFuzz has detected this issue as fixed in range 540469:540470.

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

Fuzzer: inferno_twister_c
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::Canvas2DLayerBridge::Hibernate
  void base::internal::FunctorTraits<void
  base::internal::Invoker<base::internal::BindState<void
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=539007:539008
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=540469:540470

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

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

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