Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/f537d77845c666240c8d13466e224a520612f7c5 ([async] First prototype of zero-cost async stack traces.).

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.

Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

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

commit 4111c98e7a41a9a6a51180426ce868c86f8adca8
Author: Benedikt Meurer <bmeurer@chromium.org>
Date: Fri Oct 05 06:36:27 2018

[async] Only try to peak into async functions/generators.

For --async-stack-traces don't try to peak into frames that don't belong
to async functions/generators, specifically don't try to peak into some
arbitrary builtin frames (the FrameInspector doesn't support that).

Bug:  chromium:892472 ,  chromium:892473 ,  v8:7522 
Change-Id: Idcdee26ff958c03b24dd2910bb92fc51cbc14e3c
Ref: nodejs/node#11865
Design-Document: http://bit.ly/v8-zero-cost-async-stack-traces
Reviewed-on: https://chromium-review.googlesource.com/c/1264276
Reviewed-by: Yang Guo <yangguo@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56396}
[modify] https://crrev.com/4111c98e7a41a9a6a51180426ce868c86f8adca8/src/isolate.cc
[add] https://crrev.com/4111c98e7a41a9a6a51180426ce868c86f8adca8/test/mjsunit/regress/regress-crbug-892472-1.js
[add] https://crrev.com/4111c98e7a41a9a6a51180426ce868c86f8adca8/test/mjsunit/regress/regress-crbug-892472-2.js

ClusterFuzz has detected this issue as fixed in range 56395:56396.

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8_dbg
Platform Id: windows

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  code->kind() == Code::OPTIMIZED_FUNCTION in frames.cc
  v8::platform::PrintStackTrace
  v8::internal::OptimizedFrame::GetDeoptimizationData
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=56362:56363
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8_dbg&range=56395:56396

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

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 5102254041071616 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