mslekova: your CL https://chromium.googlesource.com/v8/v8/+log/b0d09b4967c709dfd26ee0364b375e622d49841f..221e54ddbc903b42c370f285c168d9eef6dda3cb?pretty=fuller&n=10000 is the only one in the reported blame range for this bug. I see you introduced the DCHECK that's tripping here - does this indicate an underlying problem? Do you mind taking a look please, thanks!

Assigning to bmeurer (reviewer of CL) since mslekova can't be assigned security bugs.

Assigning to intern host.

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

commit 68eabceb15b9859388be33499504845c311e979e
Author: Maya Lekova <mslekova@google.com>
Date: Wed Aug 30 08:36:28 2017

Fix wrongly handled exception in CheckProxyHasTrap

Bug:  chromium:760268 
Change-Id: Id9b24ddee61926a5d1324d7da12efccf2c1eb9c2
Reviewed-on: https://chromium-review.googlesource.com/642798
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Maya Lekova <mslekova@google.com>
Cr-Commit-Position: refs/heads/master@{#47704}
[modify] https://crrev.com/68eabceb15b9859388be33499504845c311e979e/src/runtime/runtime-proxy.cc
[add] https://crrev.com/68eabceb15b9859388be33499504845c311e979e/test/mjsunit/regress/regress-760268.js

ClusterFuzz has detected this issue as fixed in range 47703:47704.

Detailed report: https://clusterfuzz.com/testcase?key=4659345337090048

Fuzzer: mbarbella_js_mutation
Job Type: mac_asan_d8_dbg
Platform Id: mac

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  __isolate__->has_scheduled_exception() in runtime-proxy.cc
  v8::internal::__RT_impl_Runtime_CheckProxyHasTrap
  v8::internal::Runtime_CheckProxyHasTrap
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=mac_asan_d8_dbg&range=47371:47372
Fixed: https://clusterfuzz.com/revisions?job=mac_asan_d8_dbg&range=47703:47704

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4659345337090048

See https://github.com/google/clusterfuzz-tools 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 4659345337090048 is verified as fixed, so closing issue as verified.

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

This bug has been closed for more than 14 weeks. Removing security view restrictions.

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