jochen @ could you please look into this and please feel free to re assigned back if needed . thanks in advance 

This might be suspected cl :

https://chromium.googlesource.com/v8/v8/+/0389df514d48c6394f606bf4e5b9b0b0cb134d1b%5E%21/src/isolate.cc

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

commit 8b8c8df05bef3238004d5a338238e53ba2115f28
Author: jochen <jochen@chromium.org>
Date: Fri Jan 20 08:57:42 2017

Also suppress exception messages thrown by native scripts

BUG= chromium:681984 
R=yangguo@chromium.org

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

[modify] https://crrev.com/8b8c8df05bef3238004d5a338238e53ba2115f28/src/compiler.cc
[add] https://crrev.com/8b8c8df05bef3238004d5a338238e53ba2115f28/test/mjsunit/regress/regress-681984.js

ClusterFuzz has detected this issue as fixed in range 42535:42536.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  AllowExceptions::IsAllowed(this) in isolate.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 42403:42404
Fixed: V8: 42535:42536

Minimized Testcase (0.09 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv94y9DfpzPyGZ-_4ypWIwUFVDKXJZ7Jhrraa5M2tygjBXtCzSucuBVaB79K5cmv1INrrMxllMGWbQioM_dnxv4g767_4W7hQbKOhhqsZtrJ7XbfQfJd8DbRS5CIQ4MZuq353cBANDK2yiVjiY-RdYcDu_AyuZOkB96R0PdjbC4Nt8Y-DDPYlkHr2JqBcmyhOqKq9ekZuf4khqEWG-zIpwCBgnJLtC2FdaVBJxjDlK55UmxyrrX92aHpV4kALC5OpuT_arPibg_QDf7Yu0kqkFjxtgmEIoxvZwS2FlKq6cmut8Im_ZGzziCFB-5vTzT9IHSRP3vIzqdNMLlDsGZXJqsswknC05r1WBNAs18C5fsPZ3qd-Adw?testcase_id=5447117578698752
function __f_0() {
  try {
    __f_0();
  } catch(e) {

      Realm.create();
  }
}
__f_0();


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

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