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

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

This seems like a potential duplicate of  issue 789896 .

ClusterFuzz has detected this issue as fixed in range 520985:521019.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

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

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

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

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

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