New issue
Advanced search Search tips

Issue 911644 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Timeout in v8_script_parser_fuzzer

Project Member Reported by ClusterFuzz, Dec 4

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=4902300809953280

Fuzzer: libFuzzer_v8_script_parser_fuzzer
Fuzz target binary: v8_script_parser_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=607560:607561

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Components: Blink>JavaScript
Owner: clemensh@chromium.org
Status: Assigned (was: Untriaged)
to CF sheriff
This is similar to 907738. Another 7kB input that runs into the timeout. Let's reduce the limit to 2kB.
Cc: mmoroz@chromium.org
Status: Started (was: Assigned)
Note: Previous such bug ( issue 907738 ) was less than a month ago.
Project Member

Comment 5 by bugdroid1@chromium.org, Dec 17

The following revision refers to this bug:
  https://chromium.googlesource.com/v8/v8.git/+/e7cdc378de877c27f243a2bbf38baf924c6e1312

commit e7cdc378de877c27f243a2bbf38baf924c6e1312
Author: Clemens Hammacher <clemensh@chromium.org>
Date: Mon Dec 17 13:39:05 2018

Reduce input size limit of parser fuzzer to 2kB

R=mmoroz@chromium.org

Bug:  chromium:911644 
Change-Id: Icc42e5ace80ea816925c95e2ea330b484b68e7cf
Reviewed-on: https://chromium-review.googlesource.com/c/1379878
Reviewed-by: Marja Hölttä <marja@chromium.org>
Commit-Queue: Clemens Hammacher <clemensh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#58280}
[modify] https://crrev.com/e7cdc378de877c27f243a2bbf38baf924c6e1312/test/fuzzer/parser.cc

Project Member

Comment 6 by ClusterFuzz, Dec 18

ClusterFuzz has detected this issue as fixed in range 617197:617205.

Detailed report: https://clusterfuzz.com/testcase?key=4902300809953280

Fuzzer: libFuzzer_v8_script_parser_fuzzer
Fuzz target binary: v8_script_parser_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=607560:607561
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=617197:617205

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
Project Member

Comment 7 by ClusterFuzz, Dec 18

Labels: ClusterFuzz-Verified
Status: Verified (was: Started)
ClusterFuzz testcase 4902300809953280 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment