Stack trace difference. Do we care? I'll add a separate suppression for this kind of stack trace difference. 

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

commit 98a1962933e87e430786de59db241abf79e97fa4
Author: machenbach <machenbach@chromium.org>
Date: Tue Jan 17 10:32:17 2017

[foozzie] Suppress stack-trace difference

BUG= chromium:681326 
NOTRY=true
TBR=rmcilroy@chromium.org,mstarzinger@chromium.org

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

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

 Issue 681339  has been merged into this issue.

ClusterFuzz has detected this issue as fixed in range 42395:42396.

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

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: 1d1
  
Sanitizer: address (ASAN)

Fixed: V8: r42395:42396

Minimized Testcase (0.43 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97Ikf2pphEtEeR-u-l3AFgonbJjXBZPUCbR5_sXyKv__-O1xBEVXZjR1KOoM-FXTM4kb82dRvdd-9PhdJiaKlRlZy67gPFAjHAx1__Yf0Viu2NDeHmrP8J9ZE1AAMCjipTUCxlVFjAUASOYwtYv0CPF5ksE1jxeGdw1tCkm43PtsrVfG0IxT5_tGqcbSswX7_6l4Sk-pHnGnzbE3aM9uWQy6eR4QkzR36NeMJakLt542LYgLlCj4yEYDZltNeNYVV67wpVUOZC6015txzihU9Ri6ShOIGrNR98l1_W4Ic0OGEJEu9Wp5MHaPNvrXMMP0Qd4TTujrNPsRnp49qxW4Rf8d-6D8WZbCUvxSe9Gs6JzmU4a85M?testcase_id=5192473061359616

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.

Comment 4 is misleading as the issue is just suppressed.

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

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

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