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/+/89f7ee10f03d696276adf1cdc901c949a2e091d4 (Adds new logging type SYSLOG which logs to the system log.).

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

I doubt this is right. The CL has nothing to do with the GPU stack this crash has happened into.

ClusterFuzz has detected this issue as fixed in range 509892:509921.

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

Fuzzer: libFuzzer_gpu_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  query_state_ == kQueryState_Pending in query_manager.h
  gpu::gles2::QueryManager::Query::UnmarkAsPending
  gpu::gles2::QueryManager::Query::MarkAsCompleted
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=419732:419790
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=509892:509921

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

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

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