-
Problem report
-
Resolution: Fixed
-
Trivial
-
6.4.4, 7.0.0alpha2
-
None
-
GNU/Linux and other Unix-like systems running zabbix_agentd.
-
Sprint 102 (Jul 2023)
-
0.4
Steps to reproduce:
- Configure vfs.fs.get[] to be polled from agent.
- Run agent under Valgrind.
Result:
==00:00:01:25.502 21904== 1,102 bytes in 27 blocks are definitely lost in loss record 38 of 40 ==00:00:01:25.502 21904== at 0x48407B4: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==00:00:01:25.502 21904== by 0x50F3789: strdup (strdup.c:42) ==00:00:01:25.502 21904== by 0x16E5E2: zbx_strdup2 (misc.c:199) ==00:00:01:25.502 21904== by 0x141ACB: vfs_fs_get_local (diskspace.c:269) ==00:00:01:25.502 21904== by 0x1339C6: zbx_execute_threaded_metric (sysinfo.c:1799) ==00:00:01:25.502 21904== by 0x1324B0: zbx_execute_agent_check (sysinfo.c:1228) ==00:00:01:25.502 21904== by 0x124CB9: process_listener (listener.c:53) ==00:00:01:25.502 21904== by 0x124CB9: listener_thread (listener.c:167) ==00:00:01:25.502 21904== by 0x151B8F: zbx_thread_start (threads.c:124) ==00:00:01:25.502 21904== by 0x121204: MAIN_ZABBIX_ENTRY (zabbix_agentd.c:1308) ==00:00:01:25.502 21904== by 0x11F423: main (zabbix_agentd.c:1593)
Expected:
No memory leak.
- caused by
-
ZBX-21892 vfs.fs.get returns wrong data if multiple file systems have identical mount point
- Closed