-
Problem report
-
Resolution: Fixed
-
Trivial
-
5.0.21
-
None
-
Windows 2012 R2, 2016, 2019
Zabbix Agent2 5.0.21
-
Sprint 87 (Apr 2022), Sprint 88 (May 2022)
-
0.5
In the Windows agent2 process memory is not managed well, so more investigation is needed
- Possible memory leaks with vfs.fs.get
We are using Agent2 for a long time with a 5m interval, A suspicious increase in zabbix_agentd.exe process memory. If you use it for several months, you can see that the memory of the agent2 process has increased significantly.
Steps to reproduce:
1. Create a host that represents a working Windows machine (tested at Windows2012 R2)
2. Add Attached template to this host
3. Start monitoring this host using a windows version of Zabbix agent2 and wait for some time
We tested "vfs.fs.get" item key with 1s intervals: memory increased 80MB per day. and If you increase the number of the same IP host settings, you can check more faster memory leaks.