Crash in gpu::gles2::GLES2DecoderPassthroughImpl::DoBindTexture |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5089351162920960 Fuzzer: afl_gpu_angle_passthrough_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: UNKNOWN WRITE Crash Address: 0x000000000000 Crash State: gpu::gles2::GLES2DecoderPassthroughImpl::DoBindTexture gpu::gles2::GLES2DecoderPassthroughImpl::DoCommands gpu::CommandParser::ProcessCommands Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=470009:470101 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5089351162920960 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
May 16 2017
Geoff, are you familiar with these fuzzers running against the pass-through command buffer?
,
May 16 2017
Also, since this configuration isn't shipping yet, downgrading to P2.
,
May 16 2017
Yep, I can take this.
,
May 16 2017
,
May 16 2017
Thanks Geoff. Let me know if I can help.
,
May 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/59d2ca1729430fc7713e642d04a772773248f030 commit 59d2ca1729430fc7713e642d04a772773248f030 Author: geofflang <geofflang@chromium.org> Date: Wed May 31 15:16:50 2017 Track currently bound external and multisample textures. This caused assertions in glBindTexture even when binding 0. Caught by the fuzzer which uses an ES 3.1 context. BUG= 726265 BUG= 719933 BUG= 719803 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/2909683002 Cr-Commit-Position: refs/heads/master@{#475912} [modify] https://crrev.com/59d2ca1729430fc7713e642d04a772773248f030/gpu/command_buffer/service/gles2_cmd_decoder_passthrough.cc
,
Jun 2 2017
ClusterFuzz has detected this issue as fixed in range 476373:476444. Detailed report: https://clusterfuzz.com/testcase?key=5089351162920960 Fuzzer: afl_gpu_angle_passthrough_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: Null-dereference WRITE Crash Address: 0x000000000000 Crash State: gpu::gles2::GLES2DecoderPassthroughImpl::DoBindTexture gpu::gles2::GLES2DecoderPassthroughImpl::DoCommands ProcessCommands Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=470009:470101 Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=476373:476444 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5089351162920960 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.
,
Jun 2 2017
ClusterFuzz testcase 5089351162920960 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by msrchandra@chromium.org
, May 9 2017Components: Internals>GPU>Internals
Labels: Test-Predator-Wrong-CLs M-60
Owner: kbr@chromium.org
Status: Assigned (was: Untriaged)