Out-of-memory in angle_translator_fuzzer |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5010389535555584 Fuzzer: libFuzzer_angle_translator_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: angle_translator_fuzzer Sanitizer: memory (MSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=475530:475596 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5010389535555584 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
,
Sep 30 2017
Re-opening the issue, as it has been incorrectly closed as WontFix. Out of Memory issues are valid bugs in most of the cases. WontFix status might be assigned only by the owner of the target code, if there is no way or no reason to prevent fuzzer from causing OOM crash. Sometimes we mark OOMs found with MSan as WontFix because MSan has big memory overhead. However, that should not be done without a proper understanding of the target as well as without looking at the crash stats.
,
Oct 4 2017
As per the Issue 668857 owner, assigning this issue to @cwallez. @cwallez -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes. Thanks.
,
Oct 4 2017
,
Oct 4 2017
Thanks for the report. This failures are caused by the shader having HUGE arrays and the translator trying to make an AST to initialize all elements. Closing as won't fix. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by kkaluri@chromium.org
, Sep 15 2017