Flushed out by shipping ignition. Needs investigation.

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

commit 72b5a0d40eb22ea22b3979af26f21e7270cbb0ce
Author: jarin <jarin@chromium.org>
Date: Mon Nov 28 12:45:06 2016

[deoptimizer] Use the correct function for handler lookup for bytecode.

BUG= chromium:668760 

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

[modify] https://crrev.com/72b5a0d40eb22ea22b3979af26f21e7270cbb0ce/src/deoptimizer.cc
[add] https://crrev.com/72b5a0d40eb22ea22b3979af26f21e7270cbb0ce/test/mjsunit/compiler/regress-668760.js

ClusterFuzz has detected this issue as fixed in range 41313:41314.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  catch_handler_frame_index < count in deoptimizer.cc
  
Regressed: V8: r41208:41209
Fixed: V8: r41313:41314

Minimized Testcase (3.08 Kb): https://cluster-fuzz.appspot.com/download/AMIfv958myVMWBOG2mAqhJnCN3_GIE8EDA5XuG2cf55yHQNcbUTMvoyZ9LB_vsOKVHQcjNEDb97BKFLZpJiWZQ1q-Hhn8lvqSleF1eSahExBZ5RMuKMJlBvhubNGqpVF45TsjWv9T65sIwoMknONQouMTatD5H-uRQ?testcase_id=6037408761249792

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

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