You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my 16 core CPU I very often have the fuzzer lock up. Contrary to #262 this happens without fuzzers crashing, but seems highly correlated to process count.
Lockups happen in 9 out of 10 times when starting the fuzzer. Applying #276 does not fix the issue. Running a CPU consuming task when starting the fuzzer makes it much more likely to "succeed".
go get -u github.com/minio/simdjson-fuzz
go get -u github.com/minio/simdjson-go
cd $GOPATH$/src/github.com/minio/simdjson-fuzz
go-fuzz-build -o=fuzz-build.zip -func=Fuzz .
go-fuzz -bin=fuzz-build.zip -workdir=corpus -procs=32
This will stop executing, either right away or after a minute or 2.
On my 16 core CPU I very often have the fuzzer lock up. Contrary to #262 this happens without fuzzers crashing, but seems highly correlated to process count.
Lockups happen in 9 out of 10 times when starting the fuzzer. Applying #276 does not fix the issue. Running a CPU consuming task when starting the fuzzer makes it much more likely to "succeed".
This will stop executing, either right away or after a minute or 2.
Example
Example 2
-v=5
output: v5-debug-output.txt.gzUsing
-procs=8
or something similar low makes the deadlock very unlikely. So it seems to be related to how fast fuzz executions are.There are several Fuzz functions
Fuzz
(used here)FuzzCorrect
,FuzzSerialize
. The deadlock happens with all, and also on other fuzzers.The text was updated successfully, but these errors were encountered: