Issue metadata
Sign in to add a comment
|
DCHECK failure in !maybe_result->IsSmi() in frames.cc |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6375193525354496 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: !maybe_result->IsSmi() in frames.cc v8::internal::JavaScriptFrame::context v8::internal::JavaScriptFrame::Print Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=46230:46231 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6375193525354496 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Oct 9 2017
Hey Michi, Looks like my CL flushed out some bug in the stack frame handling. Can you have a look? Thanks, Benedikt
,
Oct 9 2017
Repro calls "%AbortJS" directly which is not supported, this is also where the stack trace priting is triggered. This is not actionable.
,
Oct 16 2017
ClusterFuzz testcase 6375193525354496 is still reproducing on tip-of-tree build (trunk). If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase. Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
,
Nov 7 2017
,
Jan 15 2018
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 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ClusterFuzz
, Oct 9 2017Owner: bmeu...@chromium.org
Status: Assigned (was: Untriaged)