BadInputs cause unexpected behavior

[kulgg]

Description
You can find bad inputs with corresponding stack trace in unique_min_crashes and the byte input files in CrashesDeduplicatedMinimized:

Run2 Results

[kulgg]

Just to add, since i'm done with fuzzing this: If anybody wants to fuzz test in the future i pushed my NHapi-Fuzz-Environment