Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Start with analysis by paint op buffer/cc team...

Unable to provide possible suspect using Predator, CL and Code Search.
Could someone please look into the issue.

Thank You...

I'll take a look tomorrow.

ClusterFuzz has detected this issue as fixed in range 522890:522915.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e900003b5d
Crash State:
  base::OnNoMemory
  sk_out_of_memory
  throw_on_failure
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=520985:521019
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=522890:522915

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

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

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