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/+/d4214b507906607ed46248718a3642a760d64ba4 (Don't delete the invalid service id.).

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

ClusterFuzz has detected this issue as fixed in range 520200:520232.

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

Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  service_id != 0 in gles2_cmd_decoder_passthrough_doers.cc
  gpu::error::Error gpu::gles2::DeleteHelper<unsigned int, unsigned int, gpu::gles
  gpu::gles2::GLES2DecoderPassthroughImpl::DoDeleteVertexArraysOES
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=519708:519758
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=520200:520232

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md 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 6258560525926400 is verified as fixed, so closing issue as verified.

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