CHECK failure: false in query_manager.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6310647246880768 Fuzzer: libFuzzer_gpu_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: false in query_manager.cc gpu::gles2::CommandsCompletedQuery::QueryCounter gpu::gles2::QueryManager::QueryCounter Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=419732:419790 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6310647246880768 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Oct 27 2017
I think the NOTREACHED is wrong, will fix.
,
Oct 28 2017
Actually, NOTREACHED is right, we're missing some validation. Fix here: https://chromium-review.googlesource.com/c/chromium/src/+/742359
,
Oct 30 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2a8a907a26d331973f68e3bf63ecd24ad8d652fd commit 2a8a907a26d331973f68e3bf63ecd24ad8d652fd Author: Antoine Labour <piman@chromium.org> Date: Mon Oct 30 18:55:50 2017 Fix QueryCounter when target doesn't match query target Bug: 778960 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 Change-Id: Ic9db9a17fa7b7dea133673c0851bfa72b3f5ffff Reviewed-on: https://chromium-review.googlesource.com/742359 Reviewed-by: Zhenyao Mo <zmo@chromium.org> Commit-Queue: Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#512560} [modify] https://crrev.com/2a8a907a26d331973f68e3bf63ecd24ad8d652fd/gpu/command_buffer/service/gles2_cmd_decoder.cc [modify] https://crrev.com/2a8a907a26d331973f68e3bf63ecd24ad8d652fd/gpu/command_buffer/service/gles2_cmd_decoder_unittest.cc
,
Oct 31 2017
ClusterFuzz has detected this issue as fixed in range 512553:512596. Detailed report: https://clusterfuzz.com/testcase?key=6310647246880768 Fuzzer: libFuzzer_gpu_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: false in query_manager.cc gpu::gles2::CommandsCompletedQuery::QueryCounter gpu::gles2::QueryManager::QueryCounter 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=512553:512596 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6310647246880768 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.
,
Oct 31 2017
ClusterFuzz testcase 6310647246880768 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kkaluri@chromium.org
, Oct 27 2017Components: Internals>GPU
Labels: M-63 Test-Predator-Wrong
Owner: piman@chromium.org
Status: Assigned (was: Untriaged)