Testcase 5749287865810944 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.

Predator could not provide any possible suspects.

Using the CL search for the file, “frame_buffer_pool.cc” assigning to concern owner.
Suspecting Commit# https://chromium.googlesource.com/chromium/src/+/6f292c6236d2845961202307ff4b3d223b368d3d

dalecurtis@-- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.


Thank You...

ClusterFuzz has detected this issue as fixed in range 517848:517916.

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

Fuzzer: inferno_flicker
Job Type: windows_syzyasan_chrome
Platform Id: windows

Crash Type: Null-dereference
Crash Address: 0x00000003
Crash State:
  base::TaskRunner::PostTask
  media::FrameBufferPool::OnVideoFrameDestroyed
  base::internal::FunctorTraits<void
  
Memory Tool: SYZYASAN

Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=514498:517698
Fixed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=517848:517916

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

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.