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

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

Automatically adding ccs based on suspected regression changelists:

[SPv175+] Unique paint chunk ids by wangxianzhu@chromium.org - https://chromium.googlesource.com/chromium/src/+/cfa5c09fe0ff90c81380277bc95a5636faa87e8b

[SPv175+] Cache fragmented display items and paint chunks by wangxianzhu@chromium.org - https://chromium.googlesource.com/chromium/src/+/1de7bf475012870fbc4cb27aac5f2206444f5fe3

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

ClusterFuzz has detected this issue as fixed in range 526246:526248.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_tsan_chrome_mp
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x03e90000783a
Crash State:
  blink::PaintController::CopyCachedSubsequence
  blink::PaintController::UseCachedSubsequenceIfPossible
  blink::PaintLayerPainter::PaintLayerContents
  
Sanitizer: thread (TSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=526117:526127
Fixed: https://clusterfuzz.com/revisions?job=linux_tsan_chrome_mp&range=526246:526248

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

See https://github.com/google/clusterfuzz-tools 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 6543428677795840 is verified as fixed, so closing issue as verified.

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