Forum Discussion
Linux Defender Update using allot of memory up to exhaustion ?
Thanks for sharing. We opened a ticket with support, but we needed to restart all our Linux Agents.
I did find this link on Reddit and someone from Azure Support stated they open a defect. But I'm waiting for confirmation from Support. https://www.reddit.com/r/DefenderATP/comments/thb0pq/memory_consumption_in_mdatp_service_for_linux/
We've also restarted the defender services but the issue came back immediately (increased and 3 days later oom killed again processes). Is it stable now at your side?
- roger_jrMar 22, 2022Copper Contributor
Our Linux Team reverted to a older version: "
"I reverted the agent on one server from 101.58.80-1 back to 101.56.62-1 yesterday and we have not seen the memory issue on that server since. It appears to be an issue specific to 101.58.80-1."
Still waiting for a Microsoft Support Engineer to engage for our case.
- roger_jrMar 31, 2022Copper ContributorM - TAC recommended upgrading to 101.62.74 to resolve the memory/cpu issue. Basically the high cpu was a result of the memory swap caused by the memory exhaustion/leak. Our Linux Team updated to prod ver 101.62.74 and has been running in production for about a week without any memory exhaustion/leaks,
**Note to Microsoft - It would be helpful to add details into the release notes for what bugs were fixed and noted effects. This is pretty common industry practice to include the details for bug and performance fixes.**
Thanks Roger.