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

Issue 757828 link

Starred by 1 user
Status: WontFix
Owner:
ahaas@chromium.org
Closed: Sep 2017
Cc:
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Out-of-memory in v8_wasm_call_fuzzer

Project Member Reported by ClusterFuzz, Aug 22 2017 
Detailed report: https://clusterfuzz.com/testcase?key=5192406948642816

Fuzzer: libFuzzer_v8_wasm_call_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

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

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=481600:482746

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

Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Aug 24 2017

Cc: msrchandra@chromium.org
Labels: M-62 Test-Predator-Wrong
Owner: ahaas@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "v8_wasm_call_fuzzer" assigning to the concern owner who might be related.

@ahaas -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Sep 13 2017

Status: WontFix (was: Assigned)
ClusterFuzz testcase 5192406948642816 is flaky and no longer crashes, so closing issue.

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

Sign in to add a comment