CHECK failure: glGetError() == GL_NO_ERROR in feature_info.cc |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5457551222374400 Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: glGetError() == GL_NO_ERROR in feature_info.cc gpu::gles2::IsGL_REDSupportedOnFBOs gpu::gles2::FeatureInfo::InitializeFeatures Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=512880:512907 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5457551222374400 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 22 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/18afd13d94183587e05cb04031f2ee7d56ba98d9 (gpu fuzzers: AddRef on null pointers). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Dec 22 2017
,
Jan 8 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0bc7995b0c9b92373c834105431a0b9142229d90 commit 0bc7995b0c9b92373c834105431a0b9142229d90 Author: Geoff Lang <geofflang@chromium.org> Date: Mon Jan 08 22:38:57 2018 Unbind PBOs if the native PBO extension exists instead of only when exposing ES3. PBOs are still sometimes bound for internal operations when they are not exposed. BUG= 783901 BUG= 797240 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: I5243ced145ba518a2fe6a23772b388f8ae5d3e3b Reviewed-on: https://chromium-review.googlesource.com/769870 Commit-Queue: Geoff Lang <geofflang@chromium.org> Reviewed-by: Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#527790} [modify] https://crrev.com/0bc7995b0c9b92373c834105431a0b9142229d90/gpu/command_buffer/service/feature_info.cc [modify] https://crrev.com/0bc7995b0c9b92373c834105431a0b9142229d90/gpu/command_buffer/service/test_helper.cc
,
Jan 9 2018
ClusterFuzz has detected this issue as fixed in range 527783:527790. Detailed report: https://clusterfuzz.com/testcase?key=5457551222374400 Fuzzer: libFuzzer_gpu_angle_passthrough_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: glGetError() == GL_NO_ERROR in feature_info.cc gpu::gles2::IsGL_REDSupportedOnFBOs gpu::gles2::FeatureInfo::InitializeFeatures Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=512880:512907 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=527783:527790 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5457551222374400 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.
,
Jan 9 2018
ClusterFuzz testcase 5457551222374400 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 ClusterFuzz
, Dec 22 2017Labels: Test-Predator-Auto-Components