Forum Discussion
SenseNdr.exe is slowly eating the memory
Hello, For a few days now, we have some Windows Server 2019 physical machines where almot all the memory is commited to sensendr.exe. If you terminate sensendr.exe, the process comes back after...
Do you have a case number so we can cross reference in our own ticket \ escalate to our account manager? Thank you for the updates!
Our case is 2410161420001229.
- Thanks. We've opened a case referencing yours. Will keep you posted if we make any progress.
- Hello,
We patched 2 machines last Friday to first test the impact on aur applications. We started patching the other machines after that.
Unfortunately, today, on of the 2 machines started to exhibit the memory problem again; sensendr ahs already 28GB of committed memory.
We are going to watch the process to see if it will really take all the available memory because in Microsoft answer to the problem, they said 'sensendr will automatically manage and release memory before it reaches a critical level of impact'. But what is the critical level of impact ?
Sensendr maybe trying to catch up in the packets analysis until a certain time.
We will see but having already eaten up 30GB (and it is still climbing) of the 64GB available is not a good sign.seemed to kill one of our machines the other day. Our applications started failing and we couldn't RDP. One of our webservers it started having an impact.
Killing the process seems to release all the memory. I'm wondering if there is any consequence to killing SenseNdr.exe every 24 hours till it's patched.
