Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/916e35d72f4cdc6aaf39174e4f4a1a6b4297e393 (Reland ^3 "[async] Expose async hooks to d8").

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

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

commit 2d0a7649e1ad8aa4bf65b20587c7400ba2bf6e80
Author: Maya Lekova <mslekova@chromium.org>
Date: Mon Jul 23 14:34:59 2018

[async] Fix a crash when AsyncHooks is used in the proto of an object

Bug:  chromium:866315 
Change-Id: I83074475185c0646d575282d24679e18ec0628c7
Reviewed-on: https://chromium-review.googlesource.com/1146645
Commit-Queue: Maya Lekova <mslekova@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54612}
[modify] https://crrev.com/2d0a7649e1ad8aa4bf65b20587c7400ba2bf6e80/src/async-hooks-wrapper.cc
[modify] https://crrev.com/2d0a7649e1ad8aa4bf65b20587c7400ba2bf6e80/src/async-hooks-wrapper.h
[add] https://crrev.com/2d0a7649e1ad8aa4bf65b20587c7400ba2bf6e80/test/mjsunit/regress/regress-crbug-866315.js

ClusterFuzz has detected this issue as fixed in range 54611:54612.

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

Fuzzer: ochang_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: Ill
Crash Address: 0x7f19e0bd94f8
Crash State:
  v8::Utils::ReportApiFailure
  ApiCheck
  InternalFieldOK
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=54217:54218
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=54611:54612

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

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

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