ASSERT: false |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6500491186012160 Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer Fuzz target binary: swiftshader_vertex_routine_fuzzer Job Type: x86_libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: false sw::VertexProgram::WHILE sw::VertexProgram::program Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=624251:624280 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6500491186012160 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.
,
Jan 19
(3 days ago)
Automatically adding ccs based on OWNERS file / target commit history. If this is incorrect, please add ClusterFuzz-Wrong label.
,
Jan 19
(3 days ago)
Automatically assigning owner based on suspected regression changelist https://swiftshader.googlesource.com/SwiftShader/+/48d47a4912684bfa4d23d3cdaab60046bf3d0468 (Fixed all OOB accesses in VertexProgram and PixelProgram). 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.
,
Yesterday
(40 hours ago)
This is the expected behavior. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Jan 19 (3 days ago)Labels: Test-Predator-Auto-Components