Arthur Taylor
Arthur Taylor
> CI Fuzz test unexpectedly returned an error. No kidding
Uggg, The fuzzing setup isn't what I would call, easily repeatable.
Fuzzer passed, but still giving warnings...
 [error.dat.gz](https://github.com/libsndfile/libsndfile/files/9736442/error.dat.gz) Blue (dataset a) is a correct decode. Red (dataset b) is the output from seeking, yellow is the difference. The first 2048 samples are wrong....
May want to remote the ` --disable-cpu-clip disable tricky cpu specific clipper` configuration option too. IIRC, it only controls this.
Yes, it is technically a bug. However, most of the time, unless you are setting RLIMIT_AS to be very low, `malloc()` never returns null on Linux. This is called memory-overcommiting....
There are probably many instances where we don't check for null malloc return values. Yes, we can fix this, but I fear that there will still be other areas in...
We can get a MR up to fix this soon... (it's a long weekend for me :) ).
That warning message is purely informational, libsndfile is still able to read such a file. The bug is that we write such an odd-length file, that no padding byte is...
So the problem is generic to any data section that is odd in length. 101 samples of unsigned 8-bit PCM have the same issue. But it get weirder. Padding the...