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.

Automatically adding ccs based on suspected regression changelists:

Simplify FPDF_RenderPage(). by thestig@chromium.org - https://pdfium.googlesource.com/pdfium/+/84144e88da8d2bbd03ba9f8608d5603a18b4d480

Remove unused cpdf_generalstatedata.h by tsepez@chromium.org - https://pdfium.googlesource.com/pdfium/+/341422fe3beb1210b28727d08e1e6f9a6fa4b030

Watch destruction of widgets around OnAAction() method. by tsepez@chromium.org - https://pdfium.googlesource.com/pdfium/+/f8074cefb2f8d947fa83d151bcbe080b485d6e6b

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

rharrison@ can you take a look? More fuzzer image decoder timeout fun.

Looking at a profiling run, the execution is being dominated by a single pass of fetching pixels and performing a calculation based on them. Given that the input image/canvas size is specified as something like ~32k x 10k, this means there is just a lot of operations that need to be run.

Given enough time the fuzzer completes without issue. I don't think there is much for us to do, unless we have an expert on JBig2 that might know how to avoid this step.

ClusterFuzz testcase 5021905434968064 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 testcase 5021905434968064 appears to be flaky, updating reproducibility label.