Also bisects to 0655ee8fa1864ae9b735d67828bcefa5633faf9e.
Might be a duplicate of 723455.

ClusterFuzz has detected this issue as fixed in range 472196:472573.

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

Fuzzer: mbarbella_js_mutation
Job Type: linux_cfi_d8
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  1 <= target_receiver_maps.size() in ic.cc
  
Sanitizer: cfi (CFI)

Regressed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=472116:472196
Fixed: https://clusterfuzz.com/revisions?job=linux_cfi_d8&range=472196:472573

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


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 4833696153862144 is verified as fixed, so closing issue.

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

 Issue 724154  has been merged into this issue.

The fix is on the way: https://chromium-review.googlesource.com/c/517952/

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

commit 8820a79e17c71520bf8503014c5f3e700532a3eb
Author: Igor Sheludko <ishell@chromium.org>
Date: Tue May 30 09:38:48 2017

[ic] Properly handle the case when all receiver maps are deprecated.

This may happen in KeyedStoreIC when the last store via setter deprecates the receiver map.

Bug:  chromium:723366 
Change-Id: Iff19e50c3761584401340d276ab4eead111883c3
Reviewed-on: https://chromium-review.googlesource.com/517952
Reviewed-by: Toon Verwaest <verwaest@chromium.org>
Commit-Queue: Igor Sheludko <ishell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#45592}
[modify] https://crrev.com/8820a79e17c71520bf8503014c5f3e700532a3eb/src/ic/ic.cc
[add] https://crrev.com/8820a79e17c71520bf8503014c5f3e700532a3eb/test/mjsunit/regress/regress-723366.js

We have made a bunch of changes on ClusterFuzz side, so resetting ClusterFuzz-Wrong label.