New issue
Advanced search Search tips

Issue 786738 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in v8_fully_instrumented_fuzzer

Project Member Reported by ClusterFuzz, Nov 18 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5279699562659840

Fuzzer: libFuzzer_v8_fully_instrumented_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  v8_fully_instrumented_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=517631:517675

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

Issue filed automatically.

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

Comment 1 by kkaluri@chromium.org, Nov 20 2017

Cc: kkaluri@chromium.org
Components: Blink>JavaScript
Labels: M-64 Test-Predator-Wrong CF-NeedsTriage
Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

Comment 2 by titzer@chromium.org, Nov 22 2017

Status: WontFix (was: Untriaged)
The testcase repeatedly quadruples a string in size (17 times!), so it is eventually going to run out of memory.
Project Member

Comment 3 by ClusterFuzz, Nov 29 2017

Labels: Needs-Feedback
ClusterFuzz testcase 5279699562659840 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
►

Sign in to add a comment