Null-dereference READ in gl::GLApiBase::glPointParameteriFn |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5225261523271680 Fuzzer: libFuzzer_gpu_angle_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: gl::GLApiBase::glPointParameteriFn gpu::gles2::GLES2DecoderImpl::Initialize gpu::CommandBufferSetup::InitDecoder Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=513343:513367 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5225261523271680 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Nov 3 2017
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Nov 7 2017
,
Nov 7 2017
,
Nov 7 2017
,
Nov 9 2017
Unrelated to that CL. The fuzzer tries a workaround that doesn't make sense on ANGLE. I'll see if I can easily squash it, but it's not something that matters for production.
,
Nov 10 2017
ClusterFuzz has detected this issue as fixed in range 515212:515249. Detailed report: https://clusterfuzz.com/testcase?key=5225261523271680 Fuzzer: libFuzzer_gpu_angle_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000000 Crash State: gl::GLApiBase::glPointParameteriFn gpu::gles2::GLES2DecoderImpl::Initialize gpu::CommandBufferSetup::InitDecoder Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=513343:513367 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=515212:515249 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5225261523271680 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.
,
Nov 10 2017
ClusterFuzz testcase 5225261523271680 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 13 2017
,
Nov 13 2017
Shouldn't have been closed. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by pnangunoori@chromium.org
, Nov 3 2017Components: Internals>GPU>ANGLE
Labels: M-64
Owner: junov@chromium.org
Status: Assigned (was: Untriaged)