Out-of-memory in gpu_fuzzer |
||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5607886167474176 Fuzzer: libFuzzer_gpu_fuzzer Job Type: libfuzzer_chrome_msan Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: gpu_fuzzer Sanitizer: memory (MSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5607886167474176 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
,
Dec 21 2017
Unable to provide possible suspect using Predator, CL and Code Search. Could someone please look into the issue. Thank You...
,
Dec 22 2017
These issues keep coming up. I can't tell if there's something we should do. If we're going to categorically ignore them, can we somehow prevent these issues from getting filed automatically?
,
Dec 22 2017
OOM is not a fundamental issue in the GPU process, but I'll take a look to see if we can avoid running into it in the fuzzer.
,
Mar 2 2018
Pinging self.
,
Apr 17 2018
We are closing all ooms and timeouts that are unreproducible. We won't be filing such bugs in future. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ClusterFuzz
, Dec 21 2017