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

Regression from
https://chromium.googlesource.com/v8/v8/+/8c4a8250de821e1b3db381fac04efcd14dd6eb2e

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

commit 69aa6e57366360ed49deb8cf51a619280c2ae709
Author: Ulan Degenbaev <ulan@chromium.org>
Date: Fri Sep 29 10:58:00 2017

[heap] Ensure that VisitFixedArray pushes grey or black array
in marking worklist.

Bug:  chromium:769173 
Change-Id: I4b3ce27d37bec19ec5cc342b4d26a2a45af34b5f
Reviewed-on: https://chromium-review.googlesource.com/691728
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Ulan Degenbaev <ulan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#48224}
[modify] https://crrev.com/69aa6e57366360ed49deb8cf51a619280c2ae709/src/heap/incremental-marking.cc

Thank you, inferno@. This is great repro case.

ClusterFuzz has detected this issue as fixed in range 48223:48224.

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

Fuzzer: inferno_js_fuzzer
Job Type: linux_asan_d8_dbg
Platform Id: linux

Crash Type: DCHECK failure
Crash Address: 
Crash State:
  marking_state()->IsGrey(obj) || marking_state()->IsBlack(obj) in incremental-mar
  v8::internal::IncrementalMarking::VisitObject
  v8::internal::IncrementalMarking::ProcessMarkingWorklist
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48099:48100
Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48223:48224

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

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.

ClusterFuzz testcase 4559554636677120 is verified as fixed, so closing issue as verified.

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

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