Predator could not provide any possible suspects.

From the below CL observing some changes related to 'paint op buffer' , hence suspecting the same
https://chromium.googlesource.com/chromium/src/+log/3231a20b259dccb81598910a8bfa7b5dee787a9a..2eb1fe55d1eae8c706dd0611561e4f1ccea609fd?pretty=fuller&n=10000

Suspect CL: https://chromium.googlesource.com/chromium/src/+/2a9bfe4538e4b99f6adbf5b22ff65c15da6399ce

weili@ -- Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!

ClusterFuzz has detected this issue as fixed in range 555645:555651.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Out-of-memory (exceeds 2048 MB)
Crash Address: 
Crash State:
  paint_op_buffer_fuzzer
  
Sanitizer: memory (MSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=529162:529167
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=555645:555651

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

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.

ClusterFuzz testcase 5759246118158336 is verified as fixed, so closing issue as verified.

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