-
Problem report
-
Resolution: Fixed
-
Trivial
-
4.0.21rc1, 4.4.9rc1, 5.0.1rc1, 5.2.0alpha1
-
None
-
Sprint 64 (May 2020), Sprint 65 (Jun 2020)
-
0.25
==2017== 1,024 bytes in 1 blocks are definitely lost in loss record 29 of 31 ==2017== at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==2017== by 0x442A0F: zbx_malloc2 (misc.c:575) ==2017== by 0x447466: zbx_dvsprintf (str.c:738) ==2017== by 0x4475B3: zbx_dsprintf (str.c:781) ==2017== by 0x428C70: etypes_to_mask.isra.3.part.4 (dir.c:279) ==2017== by 0x428F22: etypes_to_mask (dir.c:1175) ==2017== by 0x428F22: prepare_count_parameters (dir.c:331) ==2017== by 0x428F22: vfs_dir_count (dir.c:1067) ==2017== by 0x41CA73: zbx_execute_threaded_metric (sysinfo.c:1759) ==2017== by 0x41B5BA: process (sysinfo.c:1121) ==2017== by 0x4124EA: process_listener (listener.c:57) ==2017== by 0x4124EA: listener_thread (listener.c:145) ==2017== by 0x4337AD: zbx_thread_start (threads.c:136) ==2017== by 0x40F68B: MAIN_ZABBIX_ENTRY (zabbix_agentd.c:1077) ==2017== by 0x43463F: daemon_start (daemon.c:394) ==2017== ==2017== LEAK SUMMARY: ==2017== definitely lost: 1,024 bytes in 1 blocks ==2017== indirectly lost: 0 bytes in 0 blocks ==2017== possibly lost: 0 bytes in 0 blocks ==2017== still reachable: 9,896 bytes in 241 blocks ==2017== suppressed: 0 bytes in 0 blocks ==2017== Reachable blocks (those to which a pointer was found) are not shown. ==2017== To see them, rerun with: --leak-check=full --show-leak-kinds=all ==2017== ==2017== For counts of detected and suppressed errors, rerun with: -v ==2017== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
This issue for versions 5.0.2rc1 and 5.2.0alpha1 will be fixed in ZBXNEXT-1867.