Direct-leak in spirv_cross::Compiler::build_function_control_flow_graphs_and_analyze |
|||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6370871817797632 Fuzzer: libFuzzer_dawn_spirv_cross_glsl_fast_fuzzer Job Type: libfuzzer_chrome_asan Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: spirv_cross::Compiler::build_function_control_flow_graphs_and_analyze spirv_cross::CompilerGLSL::compile GLSLFastFuzzTask Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=607427:607452 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6370871817797632 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Dec 2
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/9854295ff60b96f9c96c2711c55d2562c080dae9 (Add fuzzers for SPIRV-Cross). 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.
,
Dec 4
,
Dec 4
When I run this locally at HEAD I get an unknown address read instead of a leak from ASAN. I am not sure if this issue is related to not having the validator ahead of the cross compiler, or is a 'real' issue in the cross compiler. Once we migrate to having the validator infront of the cross compiler I will rerun this test case. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ClusterFuzz
, Dec 2Labels: ClusterFuzz-Auto-CC