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, "gl/gl_utils.cc" suspecting the below Cl might have caused this issue

Suspect CL: https://chromium.googlesource.com/chromium/src/+/3689f3e57b85ca683cc6b61841715fbd0c6af559

kbr@ -- 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 needs to stop trying to fuzz this entrypoint. It's deliberately exposed via the command line argument --enable-gpu-benchmarking only for testing purposes.

ClusterFuzz has detected this issue as fixed in range 586571:586572.

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

Fuzzer: inferno_twister
Job Type: linux_asan_content_shell_drt
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  gl::Crash
  bool IPC::MessageT<GpuChannelMsg_CrashForTesting_Meta, std::__1::tuple<>, void>:
  gpu::GpuChannel::HandleMessageHelper
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=583747:583752
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_content_shell_drt&range=586571:586572

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

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

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