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

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

related to paint op serialization?

https://skia.googlesource.com/skia/+/a088365e2faca3f28469c0fc568169e095b5b1a0/include/private/SkTemplates.h#169

Debug asserts from the fuzzer in Skia are generally WontFix.  This one looks like it handles resetting to a count of zero even though it asserts.  If there's a release issue, then we can fix it there.

sgtm- you're right code looks like it resets to zero though the assert is there

ClusterFuzz testcase 5178049598586880 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.

ClusterFuzz has detected this issue as fixed in range 553550:553569.

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

Fuzzer: libFuzzer_paint_op_buffer_eq_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x053900000849
Crash State:
  sk_abort_no_print
  SkAutoSTArray<32, float>::reset
  SkAutoSTArray<32, float>::reset
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=520972:521004
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=553550:553569

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

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.