New issue
Advanced search Search tips

Issue 713365 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

CHECK failure: !v8::internal::FLAG_enable_slow_asserts || (object->IsFixedArray()) in objects-i

Project Member Reported by ClusterFuzz, Apr 19 2017

Issue description

Comment 1 by ishell@chromium.org, Apr 21 2017

Owner: ishell@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 2 by bugdroid1@chromium.org, Apr 21 2017

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

commit ab4164ded30ea247f9a09accc5fa94e572a0416b
Author: Igor Sheludko <ishell@chromium.org>
Date: Fri Apr 21 16:57:06 2017

[debug] Fix SloppyArgumentsElements verifier.

BUG= chromium:713365 

Change-Id: I5d9d5b5e00a637923a1a3e0dc7f81fa4075c4e82
Reviewed-on: https://chromium-review.googlesource.com/484300
Reviewed-by: Jakob Kummerow <jkummerow@chromium.org>
Commit-Queue: Igor Sheludko <ishell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#44782}
[modify] https://crrev.com/ab4164ded30ea247f9a09accc5fa94e572a0416b/src/objects-debug.cc

Comment 3 by ishell@chromium.org, Apr 21 2017

Status: Fixed (was: Assigned)
Project Member

Comment 4 by ClusterFuzz, Apr 21 2017

ClusterFuzz has detected this issue as fixed in range 44781:44782.

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

Fuzzer: decoder_langfuzz
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  !v8::internal::FLAG_enable_slow_asserts || (object->IsFixedArray()) in objects-i
  
Sanitizer: address (ASAN)

Regressed: V8: 44701:44702
Fixed: V8: 44781:44782

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


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

Sign in to add a comment