ClusterFuzz has detected this issue as fixed in range 44903:44904.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_v8_arm_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  IsMarking() in incremental-marking.cc
  
Sanitizer: address (ASAN)

Regressed: V8: 44785:44786
Fixed: V8: 44903:44904

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


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.

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

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

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

commit a525d7c1643c76e18818cabcd9a6b2195505714d
Author: ulan <ulan@chromium.org>
Date: Wed May 03 10:05:41 2017

[heap] Remove TryFinalizeIdleIncrementalMarking.

We can use FinalizeIncrementalMarking instead since the only caller of
TryFinalizeIdleIncrementalMarking is IdleNotification, for which staying
within idle deadline is not critical.

This also fixes a bug caused by inconsistent code duplication in
finalization condition in the two functions.

BUG= v8:6325 , chromium:715457 

Review-Url: https://codereview.chromium.org/2851743002
Cr-Commit-Position: refs/heads/master@{#45054}

[modify] https://crrev.com/a525d7c1643c76e18818cabcd9a6b2195505714d/src/heap/heap.cc
[modify] https://crrev.com/a525d7c1643c76e18818cabcd9a6b2195505714d/src/heap/heap.h