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/+/5e79316b17b74975742522fb3f4357d75fc51a09 ([animation-worklet] Enable tests on main thread).

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.

 Issue 888231  has been merged into this issue.

The identified patch has already been reverted in https://bugs.chromium.org/p/chromium/issues/detail?id=887659#c3

We will take this crash into account when re-landing.

ClusterFuzz testcase 4686649869729792 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 597181:597205.

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

Fuzzer: inferno_twister
Job Type: mac_asan_content_shell
Platform Id: mac

Crash Type: Null-dereference READ
Crash Address: 0x000000000110
Crash State:
  blink::KeyframeEffect::StartAnimationOnCompositor
  blink::StartEffectOnCompositor
  blink::WorkletAnimation::UpdateOnCompositor
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=593278:593305
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_content_shell&range=597181:597205

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

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.