New issue
Advanced search Search tips

Issue 882233 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 10
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

V8 correctness failure in configs: x64,ignition:x64,slow_path

Project Member Reported by ClusterFuzz, Sep 9

Issue description

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,slow_path
  sources: 7dc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=55575:55576

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Sep 9

Labels: Test-Predator-Auto-Owner
Owner: szuend@google.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/a45a20e4460674f4c8a7024ea047ed29f295ddf1 ([array] Move fall-back for Array.p.shift to C++).

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

Comment 2 by bugdroid1@chromium.org, Sep 10

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

commit e365bc2dcbf3b68bd4723cebe9842a8e646511ef
Author: Simon Zünd <szuend@google.com>
Date: Mon Sep 10 09:50:52 2018

[array] Consistently throw TypeError for zero-length arrays

This CL fixes a bug that allowed calls to Array.p.shift on
zero-length arrays where the 'length' is read-only without throwing
a TypeError.

R=bmeurer@chromium.org, jgruber@chromium.org

Bug:  chromium:882233 
Change-Id: Ib129ab4c4f4f233e7bb553effa77539badfbe26e
Reviewed-on: https://chromium-review.googlesource.com/1215164
Reviewed-by: Jakob Gruber <jgruber@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Simon Zünd <szuend@google.com>
Cr-Commit-Position: refs/heads/master@{#55746}
[modify] https://crrev.com/e365bc2dcbf3b68bd4723cebe9842a8e646511ef/src/builtins/builtins-array-gen.cc
[add] https://crrev.com/e365bc2dcbf3b68bd4723cebe9842a8e646511ef/test/mjsunit/regress/regress-crbug-882233-1.js
[add] https://crrev.com/e365bc2dcbf3b68bd4723cebe9842a8e646511ef/test/mjsunit/regress/regress-crbug-882233-2.js

Status: Fixed (was: Assigned)
Project Member

Comment 4 by ClusterFuzz, Sep 11

ClusterFuzz has detected this issue as fixed in range 55745:55746.

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

Fuzzer: foozzie_js_mutation
Job Type: v8_foozzie
Platform Id: linux

Crash Type: V8 correctness failure
Crash Address: 
Crash State:
  configs: x64,ignition:x64,slow_path
  sources: 7dc
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=55575:55576
Fixed: https://clusterfuzz.com/revisions?job=v8_foozzie&range=55745:55746

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

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

Comment 5 by ClusterFuzz, Sep 11

Labels: ClusterFuzz-Verified
Status: Verified (was: Fixed)
ClusterFuzz testcase 4942775135764480 is verified as fixed, so closing issue as verified.

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

Sign in to add a comment