New issue
Advanced search Search tips

Issue 772689 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

CHECK failure: 0 == field_count_ in deoptimizer.cc

Project Member Reported by ClusterFuzz, Oct 8 2017

Issue description

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_cfi_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  0 == field_count_ in deoptimizer.cc
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=48324:48325

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 8 2017

Labels: Test-Predator-AutoOwner
Owner: bmeu...@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/v8/v8/+/279a83e4ff06c39a06a0cb5cf1612b94aa4de22e ([turbofan] Refactor the JSCreateArray lowering to support more cases.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 2 by sheriffbot@chromium.org, Oct 8 2017

Labels: M-63
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 8 2017

Labels: ReleaseBlock-Stable
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Comment 4 by sheriffbot@chromium.org, Oct 8 2017

Labels: Pri-1
Project Member

Comment 5 by bugdroid1@chromium.org, Oct 9 2017

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

commit bed88539081f5645f5162bf8efb24b0a992db18b
Author: Benedikt Meurer <bmeurer@chromium.org>
Date: Mon Oct 09 08:28:51 2017

[deoptimizer] Properly handle in-object properties on JSArrays.

The escape analysis is able to perform scalar replacement on JSArrays
with in-object properties (which currently only happens for subclasses
of the Array constructor), but the Deoptimizer didn't properly
materialized and initialized the values of the in-object fields so far.

Bug:  chromium:772689 , v8:6399
Change-Id: I6555a46773d2a1543db069142aa05f4337566b9c
Reviewed-on: https://chromium-review.googlesource.com/706781
Reviewed-by: Jaroslav Sevcik <jarin@chromium.org>
Commit-Queue: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#48365}
[modify] https://crrev.com/bed88539081f5645f5162bf8efb24b0a992db18b/src/deoptimizer.cc
[add] https://crrev.com/bed88539081f5645f5162bf8efb24b0a992db18b/test/mjsunit/regress/regress-crbug-772689.js

Status: Fixed (was: Assigned)
Project Member

Comment 7 by sheriffbot@chromium.org, Oct 9 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Project Member

Comment 8 by ClusterFuzz, Oct 10 2017

ClusterFuzz has detected this issue as fixed in range 48364:48365.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_cfi_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  0 == field_count_ in deoptimizer.cc
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=48324:48325
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=48364:48365

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

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 9 by ClusterFuzz, Oct 10 2017

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

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
Cc: jarin@chromium.org ahaas@chromium.org
Labels: -ReleaseBlock-Stable
Labels: -Test-Predator-AutoOwner Test-Predator-Auto-Owner
Project Member

Comment 13 by sheriffbot@chromium.org, Jan 15 2018

Labels: -Restrict-View-SecurityNotify allpublic
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
Project Member

Comment 14 by sheriffbot@chromium.org, Mar 27 2018

Labels: -Security_Impact-Head -M-63 M-65 Security_Impact-Stable

Sign in to add a comment