New issue
Advanced search Search tips

Issue 620253 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Fatal error in v8::FromJust

Project Member Reported by ClusterFuzz, Jun 15 2016

Issue description

Just an out of stack situation while loading a script in d8. Reproduces as follows on tip of tree ...

$ git checkout f1ac74b2530f837c905dbd7b1924220c6097acae
$ make -j1000 x64.debug
$ ./out/x64.debug/d8 boom.js
$ cat boom.js
load("boom.js");

Owner: mstarzinger@chromium.org
Status: Assigned (was: Available)
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 16 2016

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

commit e55384b28e2354b384dbbe3821af10065566231a
Author: mstarzinger <mstarzinger@chromium.org>
Date: Thu Jun 16 10:12:06 2016

[d8] Make exception reporting more resilient.

This makes sure exception reporting done by the debug shell behaves
gracefully even near the stack limit. When line number determination
fails we just fallback to not printing source information.

R=yangguo@chromium.org
TEST=mjsunit/regress/regress-crbug-620253
BUG= chromium:620253 

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

[modify] https://crrev.com/e55384b28e2354b384dbbe3821af10065566231a/src/d8.cc
[add] https://crrev.com/e55384b28e2354b384dbbe3821af10065566231a/test/mjsunit/regress/regress-crbug-620253.js

Project Member

Comment 4 by bugdroid1@chromium.org, Jun 16 2016

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

commit 424d4f3bd2da161856d18289323957a50383d19d
Author: Michael Starzinger <mstarzinger@chromium.org>
Date: Thu Jun 16 11:17:28 2016

[d8] Make exception reporting more resilient.

This is a follow-up to a recent fix to make the exception reporting even
more resilient. The original regression test flushed out more issues on
different configurations.

TBR=yangguo@chromium.org
TEST=mjsunit/regress/regress-crbug-620253
BUG= chromium:620253 
NOTREECHECKS=true

Review URL: https://codereview.chromium.org/2071783002 .

Cr-Commit-Position: refs/heads/master@{#37032}

[modify] https://crrev.com/424d4f3bd2da161856d18289323957a50383d19d/src/d8.cc

Status: Fixed (was: Assigned)
Project Member

Comment 6 by ClusterFuzz, Jun 17 2016

ClusterFuzz has detected this issue as fixed in range 37030:37031.

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

Fuzzer: decoder_langfuzz
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: Fatal error
Crash Address: 
Crash State:
  v8::FromJust
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_d8_dbg&range=29741:29742
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_d8_dbg&range=37030:37031

Minimized Testcase (7.92 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94Pn8mb2M3kMq94VbFWn9SoWMpYPEwE3-1M0pw_oDHwwjV38HkPmNw3p9onzEFJsVwtPOlvRHZsKTyQmlsavAdnSexA7YEu7F_To0qHiBvLrIFaTbJ_2Wz_t3aspVGFkPC6l3ucJDAnMYjrQKDZihGO1ceCaA

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.
Project Member

Comment 7 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

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

Sign in to add a comment