Find it and CL did not provide possible suspects.
Using Code Search for the file, "result || flags & PartitionAllocReturnNull in partition_alloc.h" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/877d29b7d92ad602c0eb80f01cd995cf4cd0f28d

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

ClusterFuzz has detected this issue as fixed in range 443650:443895.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_asan_chrome_v8_arm
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  result || flags & PartitionAllocReturnNull in partition_alloc.h
  blink::DOMTypedArray<>::createOrNull
  blink::ImageData::create
  
Sanitizer: address (ASAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=442831:443258
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_v8_arm&range=443650:443895

Minimized Testcase (0.13 Kb):
Download: https://cluster-fuzz.appspot.com/download/AMIfv95zWaY4QUB-z8d7JHF3s6QG8LQ5EJH83y_gHnY8Ioi2xRfJyZllBfhXsxHUKKAyZo9YH7jTY68-tuRHyKRupGTv_BsrysZ_KFexKNTlrFOBkrDhztSkwR-MKq2JbdCosUdH9YkTxjImZ_oASFAJvHcK5kj5TphdRDmmtaEbo8W_8mT9o9g2-CaqcWGqBwqKYHvrdpOGFHVreYKmIHWIPcHkax6ZhH50kgvJyMVrGMEXlgSjIyKgxiK7o2pPtnYMYUDoZw_NDilwflax3nwyfYefJ-Ft6DXY-LEsgDL4n3MfsvI4N2vGvU9UVBlMBdRO6F71e6KfV8rtz3rNHwf0Hj_YVfRNjCZOqmbe6PjVzblgxUTfpoQ?testcase_id=6072709831458816
<script>
var canvas = document.createElement("canvas");
var ctx = canvas.getContext("2d");
ctx.createImageData(1024, 65534);
</script>


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

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