Unable to find the suspect from find it as find it did not provide any results, below is the information:
Suspected CLs	Findit failed to find any stack trace. Is it in a new format?

From the regression range assigning it to the concern owner --
CHANGE LOG :
https://chromium.googlesource.com/v8/v8/+log/0c6fa1724f3ae2642f2f1628c10c362e01078803..71a7bca990c557a7106fa89ab6bff08b09e3b243?pretty=fuller

@ulan -- Could you please look into the issue, kindly re-assign if this is not related to your change.
Thank You.

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

ClusterFuzz has detected this issue as fixed in range 41971:41972.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4847742187995136

Fuzzer: mbarbella_js_mutation
Job Type: linux_asan_d8_ignition_v8_arm_dbg
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  committed >= used in heap.cc
  
Regressed: V8: r40971:40972
Fixed: V8: r41971:41972

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv95Gu4dXfhx2VrwfQPHGwjUwUpxDZRRilVnrGb-mUXZfqo9YsUZepXwe510mU16IbzDMl3C5OZToiPbmHQabD4Tkm_Tgh4Oh7tMafAo0M7eozSOVMnqqxewHpuJDkpa9_e2GbTk_LhyfNlf_an1j4zugHm-Kj6L_QMsp8c81mBqnIV8Xojs?testcase_id=4847742187995136


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

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