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/+/b993e42cacf1ed4454b4df62dfacf8eee2bec869 (Move Blink Sandbox IPC to Mojo Calls).

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.

Something related to the new Queue traits perhaps?

#0 0x7f7f2d4e56c9 in blink::scheduler::FrameSchedulerImpl::CreateQueueTraitsForTaskType(blink::TaskType)

ClusterFuzz has detected this issue as fixed in range 577104:577105.

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

Fuzzer: ifratric_pdf_generic
Job Type: linux_debug_chrome
Platform Id: linux

Crash Type: Ill
Crash Address: 0x7f7f2d4e56ca
Crash State:
  blink::scheduler::WebThreadScheduler::CreateMainThreadScheduler
  content::RendererMain
  content::RunZygote
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=572539:572540
Fixed: https://clusterfuzz.com/revisions?job=linux_debug_chrome&range=577104:577105

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

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

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