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 OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

+Cary (and Kevin)

hcm@ do they need to be CCed on this? I think this is exepected behavior on my fuzzer. 

I'm OK with being taken off this bug, but since it is in an area of code I'm interested in, curiosity got the better of me and I did some debugging.

A small rectangle is turned into a region through a matrix which causes the region to be very large. SkPathRef::makeSpace attempts to allocate 1G of memory; when running under GDB on Linux, I get an "out of memory" assert shortly thereafter.

I suspect that with infinite resources, the function would run a very long time but would eventually succeed. As the author suggests, the timeout is the expected behavior.

ClusterFuzz has detected this issue as fixed in range 586381:586409.

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

Fuzzer: libFuzzer_skia_image_filter_proto_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Timeout (exceeds 25 secs)
Crash Address: 
Crash State:
  skia_image_filter_proto_fuzzer
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=534725:534740
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=586381:586409

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

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

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