Maybe related to  issue 663717 .

 Issue 680312  has been merged into this issue.

 Issue 679985  has been merged into this issue.

Assigning for triage.

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

commit 29e6218b7f2e4b9886c80519b0e8443ad2fd93b3
Author: machenbach <machenbach@chromium.org>
Date: Thu Jan 12 11:49:48 2017

[foozzie] Suppress some asm test cases

BUG= chromium:680110 
TBR=clemensh@chromium.org, titzer@chromium.org, ahaas@chromium.org
NOTRY=true

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

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

ClusterFuzz has detected this issue as fixed in range 42299:42300.

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

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: 757d3b9a
  
Sanitizer: address (ASAN)

Fixed: V8: r42299:42300

Minimized Testcase (0.42 Kb): https://cluster-fuzz.appspot.com/download/AMIfv96sCAGS_t3s-6s2FrdumQHXZTfLEwQyVpSzmJSbPrqn-EhQVvWrz7b9boWBuv-OXnCF1tLZur_hEqZN13N3fNgww-PtkpgopMLmCs8tHB_U6MNyS2_6wRtfoRPTulArpidr_p-HTQWzz8gt39xFvHeVsoopDFUFq85QLV0bCf3wfH0N6CVQXSG-wOZdEpTZIWYIsW-G-fE_X96Oy2r3Z8Zo3Pgd--r5iYhF7NtANNktdL2h0LgYde3fyh6pfxq_I0GJ2qV-GaCDUe8wPEUg1KY04_yVTyOkkum5dMN4aL8JMk4kIErtr3nJjqyPSBhNBrP98iIeBEuo8fwc49uJN5_ROD6UimhhLd6eTSFk_wh8q6w7RrhTyBQik5TS7chplmpAnnqlGLbcxvQjTeaaffO2XjhBag?testcase_id=5226692407984128

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 5226692407984128 is verified as fixed, so closing issue.

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

Tracking this now as  issue 681088  as clusterfuzz closed it wrongly.