Testcase 5988157043769344 is a top crash on ClusterFuzz for windows platform. Please prioritize fixing this crash.

Marking this crash as a Beta release blocker.

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

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/+/da69d8843dc3e59e17a998231cfea40bd7d1f61c (base: Change make_scoped_refptr to WrapRefCounted.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

The suspect CL should just be a rename. It also doesn't modify any of the code in the callstack, as far as I can tell.

Predator and CL could not provide any possible suspects.
Using code search for the file, "incoming_task_queue.cc" assigning to the concern owner who might be related.

Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/a6d31c02dcf08fe03a0efac62bbdf10ee47b5e21

robliao@-- Could you please look into the issue, kindly re-assign if this is not related to your changes.


Thank You.

As noted in the suspecting commit, it's a no-op/refactor change. It just moves variable initialization to the header as well as reorders some of the fields.

ClusterFuzz has detected this issue as fixed in range 507223:507272.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: windows_syzyasan_content_shell
Platform Id: windows

Crash Type: Null-dereference
Crash Address: 0x0000004b
Crash State:
  base::debug::TaskAnnotator::RunTask
  base::internal::IncomingTaskQueue::RunTask
  base::MessageLoop::RunTask
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=506298:506316
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_content_shell&range=507223:507272

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

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

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