Null-dereference in gpu::gles2::ProgramInfoManager::Program::GetUniformsiv |
||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5585735033028608 Fuzzer: inferno_twister_c Job Type: windows_syzyasan_chrome Platform Id: windows Crash Type: Null-dereference Crash Address: 0x00000007 Crash State: gpu::gles2::ProgramInfoManager::Program::GetUniformsiv gpu::gles2::ProgramInfoManager::GetActiveUniformsiv gpu::gles2::GLES2Implementation::GetActiveUniformsiv Memory Tool: SYZYASAN Regressed: https://clusterfuzz.com/revisions?job=windows_syzyasan_chrome&range=500372:500415 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5585735033028608 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 15 2017
This appears to be a crash in ES3 code. Do we know whether clusterfuzz runs under swiftshader? If so, this may be fallout from enabling WebGL2 under swiftshader here: https://chromium-review.googlesource.com/653499 If this is the case, it's likely that we exposed an existing bug in WebGL2/ES2 that clusterfuzz was unable to catch earlier. zmo/kbr, can you take a look or reassign? Thanks!
,
Sep 15 2017
I'll take a look
,
Oct 1 2017
Automatically applying components based on information from OWNERS files. If this seems incorrect, please apply the Test-Predator-Wrong-Components label.
,
Oct 1 2017
,
Oct 18 2017
ClusterFuzz testcase 5585735033028608 is flaky and no longer crashes, 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
, Sep 11 2017Labels: Test-Predator-Wrong-CLs M-63 CF-NeedsTriage