-
Problem report
-
Resolution: Unresolved
-
Major
-
7.0.2, 7.0.3
-
Prev.Sprint, S24-W44/45
-
0.125
Steps to reproduce:
- Start Zabbix Server with default StartPreProcessor count (3)
- Monitor memory usage of Zabbix Server over time
- Note that server begins to use virtual memory instead of physical memory, behaving very much like a memory leak.
- Perform a shutdown of zabbix_server and watch the virtual memory usage go down.
- Watch running processes using a tool like top and note that the process spending the most time terminating is the preprocessing manager.
Result:
Expected:
Preprocessing manager to not use (and continue to increase usage) of virtual memory when physical memory is available.