Find it and CL did not provide any possible suspects.
Using Code Search for the file, "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.

This is an intended out of memory crash.

ClusterFuzz has detected this issue as fixed in range 453840:453876.

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

Fuzzer: cdiehl_dharma
Job Type: windows_asan_chrome
Platform Id: windows

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

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=444293:444318
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome&range=453840:453876

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95tntBbV0bpKYvBOSKXPYk_NyuHGWBRjLnTaT5bwJXMQYJVev4LaZOQrjBN0kJgQydKfeROROfmd46S-kPab_C-qKO9U22C8kjQ6VHWtgvwG4ejhnZ7MTns6a4sPIkxcxH9nFdGCD5IUezUvB8nKrGZBMGc-AUEIj03w3za8w50EAxALfPzhVH19FGVoU4_kcTbPdVA3IV3y4T8_ZxzCTOtHsVn9wKNitP4GEIslnKLazxvxJqfldST0BJZXYl7sLHlhVe0_UibkqacdrR59jHUDxheuxQYTKlY3qrGROujC6AxBl9XbydHUqLK_H4agA8OB9hcKPqP0sd4ikRVLfXo9kH7G1XueUme19Hh4Nx0lPszIAD2HaVur4ZDt7tRZFYEdHm8xAdAOerfhmBFjJ7s_NTCiw?testcase_id=4533600717635584


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.