Placeholder issue to collect results of fuzz testing as separate issues, as mentioned #5608
It seems like fuzzing IFC data to stress-test the IfcOpenShell parser might be a good idea. Typical problems would be segfaults, infinite loops and/or extreme memory usage.
I very lazily got an AI to write a fuzzing script, it isn't pretty and it needed a bit of tweaking, but it produces segfaults:
ifcfuzz.py.txt
Reactions are currently unavailable
Placeholder issue to collect results of fuzz testing as separate issues, as mentioned #5608
It seems like fuzzing IFC data to stress-test the IfcOpenShell parser might be a good idea. Typical problems would be segfaults, infinite loops and/or extreme memory usage.
I very lazily got an AI to write a fuzzing script, it isn't pretty and it needed a bit of tweaking, but it produces segfaults:
ifcfuzz.py.txt