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 assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/66bcb57a90138959ea5a42de0677ceb3cc0a40f0 (Reland "cc, gpu: Make serialization code bitness agnostic.").

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

This assert is just that the SkPictureData version is not zero.  Having it be zero doesn't seem to cause any problems, and removing the assert does not have any follow on crashes.  Therefore, I think this is just a warning to programmers and not an assert that things are going to go to awry if execution continues.  I'm going to WontFix this.

ClusterFuzz has detected this issue as fixed in range 608852:608859.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539000024d3
Crash State:
  sk_abort_no_print
  SkPictInfo::setVersion
  SkPictInfo::setVersion
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=578890:578891
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=608852:608859

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

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.