// Simple repro:

function __f_1() {
  "use asm";
  function __f_0() {
    return 0;
  }
  return {__f_0: __f_0};
}
print(Object.keys(__f_1()))


// PTAL for triage.

Call d8 once with no params once with --novalidate-asm.

 Issue 681985  has been merged into this issue.

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

commit e1fbcce8af8748b124847c28f8b562434dd284ab
Author: machenbach <machenbach@chromium.org>
Date: Wed Jan 18 10:49:39 2017

[foozzie] Fix suppressions and add one for  crbug.com/681241 

BUG= chromium:681241 
NOTRY=true
TBR=bradnelson@chromium.org,titzer@chromium.org

Review-Url: https://codereview.chromium.org/2644503002
Cr-Commit-Position: refs/heads/master@{#42446}

[modify] https://crrev.com/e1fbcce8af8748b124847c28f8b562434dd284ab/tools/foozzie/v8_suppressions.py

 Issue 682237  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 42445:42446.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6452658006392832

Fuzzer: foozzie_js_mutation
Job Type: foozzie_ignition_staging
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,fullcode:x64,ignition_staging
  sources: 61b
  
Sanitizer: address (ASAN)

Regressed: V8: 42334:42335
Fixed: V8: 42445:42446

Minimized Testcase (2.82 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96GoX5iVFKRCpgOFhJJfT0nHf9lunL0lEKD3wyjsKC4Cuho-nz6zeZHY2Xr1Zo2fAyvLAe8s3U365eM56xKIcOXlgib_OTr02kAD2f1NXa2Ole6QQDoVrpl3os1_nJbgCwWCWK6FBxX-xgIbdGl5ELyA49RYd-halVTMz85XekxDYpxfbtMkN27TXHy6DwFjN2RfQdXSCS2a7bFl8TbfRDAow1Ou-CnQ_cq24ht_gI1cdRXrxOg7nVvQE_PWQut-WCGeSW_v5YfNUEgCxhC6iUEztXoxitYt7x-6W0YToYjukfDPE6ITUTT62JugtPlwtMR5o-RGJQw5eGXAos0nLtaw4T3fIy-K87qfvHFqM2GDxoAuLY?testcase_id=6452658006392832

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

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

ClusterFuzz testcase 5922236256223232 is verified as fixed, so closing issue.

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

Is this wontfix?

Yep, this has been fixed by now.

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

commit 1dfcc4b6876d866e803b0a0af05bd27418443cbe
Author: Michael Achenbach <machenbach@chromium.org>
Date: Thu Apr 27 14:49:13 2017

[foozzie] Remove obsolete suppressions

Most of these suppressions were for the old asm-validator or for the old compiler pipeline. Some more are just optimistically removed.

Bug:  chromium:681088 ,  chromium:681241 , chromium:681806,  chromium:662840 
NOTRY=true

Change-Id: I4c6851a72d22070026eeaca90ad3394cfce10f90
Reviewed-on: https://chromium-review.googlesource.com/488641
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Reviewed-by: Michael Starzinger <mstarzinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#44942}
[modify] https://crrev.com/1dfcc4b6876d866e803b0a0af05bd27418443cbe/tools/foozzie/v8_foozzie_test.py
[modify] https://crrev.com/1dfcc4b6876d866e803b0a0af05bd27418443cbe/tools/foozzie/v8_suppressions.py

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.