Issue metadata
Sign in to add a comment
|
Unknown exception in Register, libglesv2.dll |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4583672144723968 Fuzzer: inferno_layout_test_unmodified Job Type: windows_asan_chrome Platform Id: windows Crash Type: Unknown exception Crash Address: 0x007ed088 Crash State: Register Register Register Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=512219:512265 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4583672144723968 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 29 2017
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/cff80254855685dd43a0a42eae3b3866ce3f0a41 (Move broker_process_ from policies to SandboxLinux itself). If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
,
Dec 29 2017
,
Dec 29 2017
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 29 2017
,
Dec 29 2017
I'm not sure how the auto-triage works, but the SwiftShader roll in the regression range contained a few changes that seem more likely culprits. https://swiftshader.googlesource.com/SwiftShader.git/+log/ec5da19..6e27fea
,
Jan 2 2018
Thanks. The roll contains the commits creating the fuzzer, so this is a pre-existing bug. Assigning to capn@
,
Jan 2 2018
Canvas is huge (17000x17000) so it runs out of memory. Crashing the GPU process is acceptable/expected behavior.
,
Jan 25 2018
,
Feb 2 2018
ClusterFuzz testcase 4583672144723968 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Feb 2 2018
Because we now have symbols for SwiftShader, clusterfuzz probably no longer identifies it as a crash in Register(), and this will probably pop up again with a new stack trace.
,
May 12 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Dec 29 2017Labels: Test-Predator-Auto-Components