I've been using ProcWatch for a few weeks now and generally find it really useful for catching processes that slowly start consuming more memory or handles than they should. I'm currently running it on Windows 11 24H2, with ProcWatch 1.0.0.0, and I've noticed a strange issue with the alert history. I set up a rule to warn me when a process goes above 2 GB private memory or 50,000 handles. Everything works normally while the process is running. For example, Chrome triggered the memory warning after several hours, and ProcWatch correctly identified the process and showed the alert. The problem starts after I close the application. Even after confirming in Task Manager that all of its processes have disappeared, the old ProcWatch alert sometimes remains active in the monitoring window. If I start Chrome again, ProcWatch can then show another entry for Chrome, so I end up with what looks like a duplicate/stale entry for the same application. I've also noticed this with a couple of other applications, although it doesn't happen every time. It seems more likely when the application has several child processes and they terminate at slightly different times. Waiting several minutes doesn't always clear the old entry. Has anyone else experienced stale process entries or alerts remaining after the process has terminated? Is there a setting I'm missing for how ProcWatch handles terminated processes, or is this potentially a bug in the process monitoring/alert cleanup?
We've now fixed a bug that could cause duplicate entries in the Recent Events list. That may be what you saw. If you see it again after updating, please let us know.
Highlights for currently triggered rules were also added.
Thanks for the feedback!