Unable to find any suspect for this, could anyone from gpu team take a look into this.

https://codereview.chromium.org/2747823004/ should fix this.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/bbd052efa719a473ee143cdb8f6e84bcbfbf0876

commit bbd052efa719a473ee143cdb8f6e84bcbfbf0876
Author: piman <piman@chromium.org>
Date: Tue Mar 14 17:36:39 2017

Fix QueryCounter on a pending query

BUG= 699481 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2747823004
Cr-Commit-Position: refs/heads/master@{#456753}

[modify] https://crrev.com/bbd052efa719a473ee143cdb8f6e84bcbfbf0876/gpu/command_buffer/service/query_manager.cc
[modify] https://crrev.com/bbd052efa719a473ee143cdb8f6e84bcbfbf0876/gpu/command_buffer/service/query_manager_unittest.cc
[modify] https://crrev.com/bbd052efa719a473ee143cdb8f6e84bcbfbf0876/ui/gl/gpu_timing_fake.cc

ClusterFuzz has detected this issue as fixed in range 456708:456753.

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

Fuzzer: libfuzzer_gpu_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  query_state_ == kQueryState_Initialize || query_state_ == kQueryState_Paused || 
  gpu::gles2::QueryManager::Query::MarkAsActive
  gpu::gles2::TimeStampQuery::QueryCounter
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=455091:455226
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=456708:456753

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv963UIcopWReB-wrzCyoT3jG9SBUdBarSO1WRjDHWpMiiPRq639mAJ8Uc1jYeYD3BFVduQ5dNJhKlMuAkw0Rc3CaOhgqrNAb2AZqC5EAo4YqiQcOElYzYz8lnZasIDy57FWoh7LQ7oYSlyvlhGemKTuqjZsMMwFcjvYouG0ANKs3ToMKACj8Gr2vkUKOfzqwNCeqCBzdFC7U4fcOnddMov06ZOZbszozXLUYUvRK81RLOcm6dSsxIu4WUChNPxTVhV7Jv7zlnRI-a3hJNX2ZN9i7F2FYJ2KHeCM-lprBCfP47cFOkRK-6muoHZl4GSwmBZtEdtRPqVuoA-2-uTAm7MzE89XeK1qvNMFdkmEnAhEQWkqnn08?testcase_id=4653200708993024


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

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