New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 835415 link

Starred by 2 users
Status: Duplicate
Merged: issue 839226
Owner:
ahass...@chromium.org
Closed: May 2018
Cc:
manojgupta@chromium.org
█ senj@google.com
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in puffin_fuzzer

Project Member Reported by ClusterFuzz, Apr 20 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5539096823595008

Fuzzer: libFuzzer_puffin_fuzzer
Job Type: libfuzzer_asan_chromeos
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  puffin_fuzzer
  
Sanitizer: address (ASAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5539096823595008

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
Project Member

Comment 1 by ClusterFuzz, Apr 20 2018

Cc: ahass...@google.com senj@google.com
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file.

If this is incorrect, please add ClusterFuzz-Wrong label.

Comment 2 by infe...@chromium.org, Apr 23 2018 

 Issue 833117  has been merged into this issue.

Comment 3 by infe...@chromium.org, Apr 23 2018

Cc: -ahass...@google.com
Owner: ahass...@chromium.org
Status: Assigned (was: Untriaged)
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.
Project Member

Comment 4 by ClusterFuzz, Apr 27 2018

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5539096823595008 appears to be flaky, updating reproducibility label.

Comment 5 by ahass...@chromium.org, May 1 2018 

I investigated this, and the failure does not seem to be a problem. Basically due to input, a malloc size of around 570MB is requested, which seems to take a few seconds to allocate and that is why we get the timeout. We do not want to restrict the size of the buffer so this basically won't fix.

Comment 6 by infe...@chromium.org, 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.

Comment 7 by infe...@chromium.org, May 5 2018

Mergedinto: 839226
Status: Duplicate (was: Assigned)
We renamed the fuzz targets to include chromeos_ prefix.

Comment 8 by ahass...@chromium.org, May 7 2018 

> We renamed the fuzz targets to include chromeos_ prefix.

What is this information for? Is it a request to change the name of the fuzzers?

Comment 9 by manojgupta@chromium.org, May 7 2018 

I think it is about the title in the dup bug that refers to chromeos_puffin_fuzzer instead of puffin_fuzzer ( https://bugs.chromium.org/p/chromium/issues/detail?id=839226 )

Comment 10 by ahass...@chromium.org, May 7 2018 

Ah, I see, thanks.
►

Sign in to add a comment