Predator could not provide any possible suspects.
Using the CL search for the file, “gpu.cc” assigning to concern owner.

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

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


Thank You.

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

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

ClusterFuzz has detected this issue as fixed in range 512571:512601.

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

Fuzzer: attekett_surku_fuzzer
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x00000001
Crash State:
  [vdso]
  ui::Gpu::EstablishGpuChannelSync
  content::RenderThreadImpl::EstablishGpuChannelSync
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=512306:512363
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_v8_arm&range=512571:512601

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

Additional requirements: Requires Gestures

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

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