Issue metadata
Sign in to add a comment
|
CHECK failure: 0 == field_count_ in deoptimizer.cc |
||||||||||||||||||||||
Issue descriptionDetailed 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.
,
Oct 8 2017
,
Oct 8 2017
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
,
Oct 8 2017
,
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
,
Oct 9 2017
,
Oct 9 2017
,
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.
,
Oct 10 2017
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.
,
Oct 10 2017
,
Nov 3 2017
,
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
,
Mar 27 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Oct 8 2017Owner: bmeu...@chromium.org
Status: Assigned (was: Untriaged)