Abrt in gpu::CommandBufferSetup::LogGLDebugMessage |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6610180561960960 Fuzzer: afl_gpu_angle_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: Abrt Crash Address: 0x053900004157 Crash State: gpu::CommandBufferSetup::LogGLDebugMessage gl::Debug::insertMessage gl::Debug::insertMessage Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=523272:523295 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6610180561960960 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
May 19 2018
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
May 19 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/7b9fe37fc214c456257f79ff6e9c76d37657100d (Revert "Logging to ensure that non-offscreen surfaces are destroyed as expected"). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
May 21 2018
Geoff, could you take a look? I think it has to do with attaching a compressed texture to a framebuffer, which is not a great idea - I expect an incomplete framebuffer - but isn't disallowed by the spec, however it looks like ANGLE raises GL_INVALID_OPERATION.
,
Jun 19 2018
,
Jul 23
The following revision refers to this bug: https://chromium.googlesource.com/angle/angle/+/3003f0484d1af40dbaf2510564bdb1fc0f43bdab commit 3003f0484d1af40dbaf2510564bdb1fc0f43bdab Author: Yuly Novikov <ynovikov@chromium.org> Date: Mon Jul 23 20:23:34 2018 Don't generate error for compressed texture formats in glFramebufferTexture2D This validation error was added in 0186813531a7e8f47d584ca7fb54a73ed99d19be without explanation. Shouldn't be an error according to GLES 2.0.25 spec. Bug: 844846 Change-Id: Idc6d4d76304cbede7aa6d96bdccaefec40272b84 Reviewed-on: https://chromium-review.googlesource.com/1147149 Reviewed-by: Antoine Labour <piman@chromium.org> Reviewed-by: Geoff Lang <geofflang@chromium.org> Commit-Queue: Yuly Novikov <ynovikov@chromium.org> [modify] https://crrev.com/3003f0484d1af40dbaf2510564bdb1fc0f43bdab/src/libANGLE/validationES2.cpp
,
Jul 24
ClusterFuzz has detected this issue as fixed in range 577319:577346. Detailed report: https://clusterfuzz.com/testcase?key=6610180561960960 Fuzzer: afl_gpu_angle_fuzzer Job Type: afl_chrome_asan Platform Id: linux Crash Type: Abrt Crash Address: 0x053900004157 Crash State: gpu::CommandBufferSetup::LogGLDebugMessage gl::Debug::insertMessage gl::Debug::insertMessage Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=523272:523295 Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=577319:577346 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6610180561960960 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.
,
Jul 24
ClusterFuzz testcase 6610180561960960 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
, May 19 2018Labels: Test-Predator-Auto-Components