Unable to find actual suspect through code search and also observing no CL's under regression range, hence adding appropriate label and requesting someone from dev team to look in to this issue.

Here is the change log: https://chromium.googlesource.com/chromium/src/+log/a416210a47f892615e3e3ef493b74320100e4c67..f302efe3d406be0c40a20886dde91cfaedbe7ff5?pretty=fuller&n=10000

pcc@, can you please see if this change (https://chromium.googlesource.com/chromium/src/+/66bcb57a90138959ea5a42de0677ceb3cc0a40f0) is related? Not very sure if this is OOM.

Thank you!

Removed this fuzzer.

ClusterFuzz has detected this issue as fixed in range 608850:608881.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  paint_op_buffer_eq_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=578887:578897
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=608850:608881

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.