We've been fixing these as quickly as we can. Are there more issues then what have been filed? Some more context on which crashes are the most important or if there are issues which we haven't previously assigned would be greatly appreciated.

Steven, could you PTAL?

Please see the logs on https://clusterfuzz.com/v2/performance-report/libFuzzer_spvtools_opt_size_fuzzer/libfuzzer_chrome_asan/2018-10-30

The bugs filed are here: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=spvtools+label%3AClusterFuzz&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids

K, we'll take a look at the filed bugs. The logs don't give the test cases
that I can see, just a stacktrace?

Thanks,
dan

The logs don't have the testcases, but the bugs have them.

Is this for Linux?

Yes

We've fixed a bunch of the blocking bugs. One remaining one is a large refactor to fix that we're working on.

I don't see any input files linked from the logs so there is nothing we can do with those. Please file bugs with attached reproduction cases if you still think the crash rate is too high.