Timeout in dawn_spirv_cross_hlsl_fast_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5987250992840704 Fuzzer: libFuzzer_dawn_spirv_cross_hlsl_fast_fuzzer Job Type: windows_libfuzzer_chrome_asan Platform Id: windows Crash Type: Timeout (exceeds 25 secs) Crash Address: Crash State: dawn_spirv_cross_hlsl_fast_fuzzer Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=609745:609746 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5987250992840704 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing_on_windows.md for more information.
,
Nov 30
rharrison@, just wondering do you have any inputs here?
,
Dec 1
ClusterFuzz testcase 5987250992840704 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 4
This is another issue related to the fact SPIRV-cross allocates storage for all potential ids during initialization. This normally expresses itself as a memory usage limit issue, but in this case it is timing out before it can overrun its memory limit. This will either be resolved by performing some sort of optimization in the new shaderc wrapper for this code or directly resolving https://github.com/KhronosGroup/SPIRV-Cross/issues/781.
,
Dec 14
The documentation for reproducing on Windows has been moved to https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kkaluri@chromium.org
, Nov 28Labels: M-72 Test-Predator-Wrong CF-NeedsTriage