oss-fuzz/projects/mpg123
Thomas Orgis 356f2b9476 mpg123: limit fuzzer runtime (#2832)
* mpg123: limit runtime of decode_fuzzer

To avoid spurious timeout reports, the test shall end after 10000 MPEG frames
or 1 MiB of data, which should both be reasonable numbers. The timeout
report motivating this had 500K with 140k bad frames. The limit of
10000 frames corresponds to a normal radio song as MP3 stream.

* mpg123: limit runtime of read_fuzzer

This applies the same logic as the decode fuzzer: stop decoding after
10000 MPEG frames or 1 MiB of input data. We could debate a bigger
limit on the data size, but we do want compact testcases, right?
2019-09-16 07:06:25 -07:00
..
Dockerfile [mpg123] Use FuzzedDataProvider instead of byte_stream. (#2810) 2019-09-06 09:47:12 -07:00
build.sh
decode_fuzzer.cc mpg123: limit fuzzer runtime (#2832) 2019-09-16 07:06:25 -07:00
project.yaml
read_fuzzer.c mpg123: limit fuzzer runtime (#2832) 2019-09-16 07:06:25 -07:00