pfSense

Leaving `pftop` running in an interactive session for an extended period (several hours to days) causes continuous memory usage growth, leading to a point where kernel triggers OOM (Out-of-Memory) kill to save the system. Despite having 16GB RAM, this was enough to put the system in critical state. Suricata and other services were stable and consistent in memory usage.

Reproduction Steps

1. Open terminal or SSH into pfSense+
2. Run `pftop` and leave it running for several hours to days (especially with high session counts)
3. Monitor memory usage (`top`, `vmstat`, `swapinfo`)
4. System eventually reaches high memory usage (98–100%)
5. Kernel fails to reclaim memory and force kills `pftop`

Expected Behavior

`pftop` should:
- Not consume growing memory over time
- Be safely reclaimable by kernel
- Not lead to system-wide instability