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

commit 310f9213773ee5d314d2b2ca9b2112327a23baf5
Author: Michael Achenbach <machenbach@chromium.org>
Date: Tue Feb 14 15:00:19 2017

[foozzize] Properly encode/decode captured output

BUG= chromium:691954 
NOTRY=true
R=​​tandrii@chromium.org
TBR=jarin@chromium.org

Change-Id: Id57ed8206a19abb09a7e9835c876d3a932405658
Reviewed-on: https://chromium-review.googlesource.com/442424
Reviewed-by: Michael Achenbach <machenbach@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#43190}
[modify] https://crrev.com/310f9213773ee5d314d2b2ca9b2112327a23baf5/tools/foozzie/v8_foozzie.py

ClusterFuzz has detected this issue as fixed in range 43189:43190.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  suppression: internal_error
  
Sanitizer: address (ASAN)

Fixed: V8: 43189:43190

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95fFvyG3ZYkR9NMvcJRbgu4eLo4g4zork8ArTXcHaIOBzZRKflm5GV8srQUnvET-eiUQcrpd2kDqmVKtRDq-auHYQSE-QyroW0HSqmz4YZpN6UozENl7-siB5vxQMRaOfL1To4TJMgNWi74doDzHPBwwZi_zt0YY9hzPTlyuxWCB9fOjDinGoYFxFj-musvufBogQTi15_KeMqeSgkSd2qE03Krjx01f9HMUKZIlDlSBddY_FXz2gx_JIXZ5UgBzrUvpZ0rm10LuSwb3DYX_c9ft3PJi1ueFZZ5Rz8LLQTw5BGEseVoKSmJcL92Pebsgj_gKWWYUahK0YSfL6alglvkekBWfI8lxoXuqWN5badQFmhipZMUgeprDhfpv183m61xr51JyEFnKAYH22In81YWcms0hw?testcase_id=6051257375784960


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.