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/+/c94bb454de9f708d00da0b3cba5f7a25f99dace6 (Pass per-frame task runner to mojo::Binding in renderer.).

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.

Hmm, I couldn't reproduce this with the build options (CFI)

ClusterFuzz has detected this issue as fixed in range 616187:616216.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_cfi_chrome
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  blink::LockManager::LockRequestImpl::LockRequestImpl
  blink::LockManager::LockRequestImpl* blink::ConstructTrait<blink::LockManager::L
  blink::LockManager::request
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=615851:615860
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_chrome&range=616187:616216

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

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

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