Suricata

Due to a logic error / missing logic in file tracker truncing, the post-GAP truncing didn't actually clear the stored out of order chunks or prevent new chunks for being stored. This could quickly exhaust every available memory.

The problem is mitigated by the max-read-queue-size setting, but this setting is not enabled by default.