Issue metadata
Sign in to add a comment
|
Out-of-memory in puffin_fuzzer |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6393087786745856 Fuzzer: libFuzzer_puffin_fuzzer Job Type: libfuzzer_asan_chromeos Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: puffin_fuzzer Sanitizer: address (ASAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6393087786745856 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Apr 23 2018
,
Apr 23 2018
ahassani@, please note that we create one crash state for an oom and timeout crashes. so if fix one, these can be different variant of oom, timeout. please look at stacktrace for more info.
,
Apr 27 2018
ClusterFuzz testcase 6393087786745856 appears to be flaky, updating reproducibility label.
,
May 1 2018
Same as crbug.com/835415 this issue is request for large buffer. This won't fix. Is there any way we can skip these kind of issues?
,
May 2 2018
Specify a testcase size limit, see last point in https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/getting_started.md#improving-your-fuzz-target. then mark this fixed.
,
May 2 2018
It is not the testcase size itself. It is the content of the test case that creates causes us to request a large buffer. For example somewhere in the test case, an integer constitutes a very large number and we use that to create a buffer we need. If these errors cannot be skipped, I see no other way except to remove the puffpatch fuzzer. (We can still keep puff and huff fuzzers).
,
May 5 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Apr 20 2018Labels: ClusterFuzz-Auto-CC