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

Issue 672169 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jan 2017
Cc:
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, Dec 7 2016

Issue description

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong
Owner: ahaas@chromium.org
Status: Assigned (was: Untriaged)
Find it did not find provide any possible suspect.
Assigning to the concern owner from the regressed range -
https://chromium.googlesource.com/chromium/src/+log/83ae56bab030686ec47692edf2243dfcd680e7a7..255ac214e64d62812ca7e65492de844ace019fb4?pretty=fuller


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

Comment 2 by ClusterFuzz, Jan 7 2017

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

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

Sign in to add a comment