Handle panics and infinite loops found via fuzzer

[eric]

By doing some basic fuzzing I was able to find some panics and an infinite loop.

I've let it run for 20 minutes and haven't found any additional issues yet.

[asticode]

I'm really not familiar with fuzzing but those are really good catch 👍

Could you explain a little bit how you came up with the testdata?

[eric]

Could you explain a little bit how you came up with the testdata?

I grabbed the first 1880 bytes from 6 different MPEG-TS streams I had laying around as the start and then the fuzzer automatically writes additional files as there are failures.

I then took the .ts files and used file2fuzz from golang.org/x/tools/cmd/file2fuzz@latest to convert them to testdata.

You can read up more about fuzzing here: https://go.dev/security/fuzz/

The system will take the initial data you give it as a starting point and then will create random permutations that it uses to explore what could cause the code under test to fail (crash in our case).

To run the fuzzer:

$ go test -fuzz FuzzDemuxer

[asticode]

Thanks a lot for the explanation! I'll dig a little bit deeper with the link you've provided 👍