What I mean is the following:
When I run HostMonitor as a service, it wil not have the right to generate a pop-up menu (interaction with the desktop is not possible). And if they would appear on the desktop, I wil never see them, using a terminal service session.
When I run HostMonitor as an application, it has the right to generate a pop-up menu (interaction wiht the desktop is possible).
So I only "see" the pop-up messages when I start HostMonitor as an application. But in both cases, I get the same message in the event viewer and I do not know if the last report generated is the correct one! (most likely not).
So yes this should be investigated. Especially since Windows itself has no lack of memory!
Since multiple pop-up messages appear, it is obvious that HostMonitor itself does not stop. This means that comparing resource usage before and after the (non-generated) pop-up messages (if HostMonitor is running as a service) should not result in any 'leakage'.
I never said it was a memory leak

But perhaps one part of the application needs more but doesn't request or get more memory. And be assured, I do know how resource allocation works and also how you can mess up a system when you incorrectly work with it
