New issue
Advanced search Search tips

Issue 827779 link

Starred by 2 users
Status: WontFix
Owner:
cbruni@chromium.org
Closed: Apr 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Reference Error causes Crash

Project Member Reported by ClusterFuzz, Mar 31 2018 
Detailed report: https://clusterfuzz.com/testcase?key=6048750225850368

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: Fatal error
Crash Address: 
Crash State:
  
  v8::platform::PrintStackTrace
  v8::internal::Runtime_AbortJS
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=51276:51277

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, Mar 31 2018

Labels: Test-Predator-Auto-Owner
Owner: cbruni@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/52b3b491a55f5f3233ca78e0c22c37384b92670e ([errors] Use FATAL macro where possible).

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.

Comment 2 by cbruni@chromium.org, Apr 3 2018

Summary: Reference Error causes Crash (was: Fatal error in )

Comment 3 by cbruni@chromium.org, Apr 16 2018

Status: WontFix (was: Assigned)
 eval("%AbortJS(message)") will crash, thank you :)
Project Member

Comment 4 by ClusterFuzz, Apr 23 2018

Labels: Needs-Feedback
ClusterFuzz testcase 6048750225850368 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.
►

Sign in to add a comment