New issue
Advanced search Search tips

Issue 832126 link

Starred by 1 user
Status: Assigned
Owner:
infe...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in string_tokenizer_fuzzer

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

Fuzzer: libFuzzer_string_tokenizer_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  string_tokenizer_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=545925:545931

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

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 12 2018

Labels: Test-Predator-Auto-Owner
Owner: infe...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/3277b80e5f0fa6ccdcf4c8e85be8b54b2dc66f36 (Allow large pattern size in string tokenizer fuzz target.).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Project Member

Comment 2 by ClusterFuzz, Jun 30 2018

Labels: OS-Mac
Project Member

Comment 3 by ClusterFuzz, Oct 14

Labels: OS-Windows
Project Member

Comment 4 by ClusterFuzz, Dec 1

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

Comment 5 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
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.

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

Comment 7 by ClusterFuzz, Dec 6

Labels: OS-Chrome
►

Sign in to add a comment