Closed Shnatsel closed 5 months ago
This is a bug in fdeflate
that was fixed in version 0.3.4.
We should probably see about getting you access to the oss-fuzz so you can see crashes detected there. I think it might just be a matter of adding a address gmail here?
I can still reproduce this with a different file even on fdeflate
v0.3.4: crash-7015e5b72205faf10ae3174f531837d665955b1a
Weirdly, neither file reproduces for me with fdeflate
v0.3.4
Oh, I ran cargo update
in the root directory but not in the fuzz
directory. My bad!
No more issues after 2.4 billion fuzzer executions :tada:
Decoding the following image results in a panic: crash-095de1cef9395bc69ebcb9250ee27b485989f282
Found by
cargo fuzz
on commit 5ac3b4189119895f4e47a4391e86e6955855d8e0Also, after the recent performance optimizations the fuzzer goes absolutely BRRRRRR. I'm getting over 100,000 executions per second per core, I have never seen anything like it :rocket: