Regression range points to: https://crrev.com/6d0a4202982529630e7f7e636b25f267b7fe8857

This can not happen in the wild, since the natives syntax is not used outside of testing and V8's native JS code. I will upload a fix to turn the crash into a syntax error though.

Yeah, should still be a safe SyntaxError though. Otherwise code that safely throws SyntaxError cannot be run with --allow-natives-syntax anymore.

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

commit 986814218b907cbac244a3624362ee9351f6badb
Author: yangguo <yangguo@chromium.org>
Date: Mon Jul 25 05:32:11 2016

Native try-catch syntax parsing should not crash.

R=littledan@chromium.org
BUG= chromium:630559 

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

[modify] https://crrev.com/986814218b907cbac244a3624362ee9351f6badb/src/parsing/parser.cc
[add] https://crrev.com/986814218b907cbac244a3624362ee9351f6badb/test/mjsunit/regress/regress-crbug-630559.js

ClusterFuzz has detected this issue as fixed in range 37995:37996.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_v8_arm_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  Token::CATCH == tok in parser.cc
  
Regressed: V8: r37965:37966
Fixed: V8: r37995:37996

Minimized Testcase (0.04 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv97HroIxqnKayu-8l_F1uZYSXRsrSq3cjKgUSEnSpb1BvCPpOPZIAD4qsNOHT4kFLwHZRtN2tkbOEgxSW6Cjj23tt1l-PNEDydrh0c4DoUl98-B0hHeccMVXN3biUccs7Bi-pD6i0QiCQ_pHBiGKhEnGjVUCiQ?testcase_id=6304143111356416
try {
}
%OptimizeFunctionOnNextCall();


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.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot