Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Predator and CL could not provide any possible suspects.

Using Code Search for the file, "gpu_data_manager_impl_private.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/5d7fb33e82c0b4fae533189f0332d1f45a3fb457

kylechar@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 583932:583936.

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

Fuzzer: ipc_fuzzer_mut
Job Type: linux_asan_chrome_ipc
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000ea3
Crash State:
  content::GpuDataManagerImplPrivate::FallBackToNextGpuMode
  content::GpuDataManagerImpl::FallBackToNextGpuMode
  content::GpuProcessHost::RecordProcessCrash
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_ipc&range=583932:583936

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

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

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