Issue metadata
Sign in to add a comment
|
DCHECK failure in !backing_store->is_the_hole(isolate, i) in elements.cc |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5521488504684544 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: !backing_store->is_the_hole(isolate, i) in elements.cc ValidateContents ValidateImpl Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48861:48862 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5521488504684544 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Nov 17 2017
,
Nov 18 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
,
Nov 18 2017
,
Nov 19 2017
Fix in flight: https://chromium-review.googlesource.com/c/v8/v8/+/776696
,
Nov 19 2017
,
Nov 21 2017
ClusterFuzz has detected this issue as fixed in range 49480:49481. Detailed report: https://clusterfuzz.com/testcase?key=5521488504684544 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: !backing_store->is_the_hole(isolate, i) in elements.cc ValidateContents ValidateImpl Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48861:48862 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=49480:49481 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5521488504684544 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.
,
Feb 27 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 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Nov 17 2017Owner: danno@chromium.org
Status: Assigned (was: Untriaged)