The following corpus directories contain some very large input files which unnecessarily cause the fuzzing runtime to exceed what feels reasonable.
"Unnecessarily large" in this context means that the presence of these very large input files do not add any coverage beyond what is already achieved by processing only significantly smaller input files already in the corpus.
| Corpus directory | Largest coverage increasing file in directory | Largest input file in directory |
|---|---|---|
addrman |
143 118 bytes | 1 048 576 bytes |
banman |
49 814 bytes | 50 125 bytes |
block |
1 000 431 bytes | 1 048 576 bytes |
prevector |
709 301 bytes | 709 301 bytes |
process_messages |
984 807 bytes | 3 984 182 bytes |
script_flags |
961 741 bytes | 1 855 780 bytes |
transaction |
111 109 bytes | 111 872 bytes |
Perhaps we should consider removing these excessively large inputs that do not add any coverage at the moment and are unlikely to do so in the future?
