Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
3.4.4
-
None
-
None
Description
Valgrind reports the following memory leak when using the c-client (mt):
==11674== 18 bytes in 9 blocks are indirectly lost in loss record 14 of 173
==11674== at 0x4C2B6CD: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==11674== by 0xC8064A: ia_deserialize_string (recordio.c:271)
==11674== by 0xC81F2E: deserialize_String_vector (zookeeper.jute.c:247)
==11674== by 0xC842F9: deserialize_GetChildrenResponse (zookeeper.jute.c:874)
==11674== by 0xC7E9F0: zookeeper_process (zookeeper.c:1904)
==11674== by 0xC7FE5B: do_io (mt_adaptor.c:439)
==11674== by 0x4E39E99: start_thread (pthread_create.c:308)
==11674== by 0x5FA6DBC: clone (clone.S:112)
==11674==
==11674== 90 (72 direct, 18 indirect) bytes in 49 blocks are definitely lost in loss record 139 of 173
==11674== at 0x4C29DB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==11674== by 0xC81EEE: deserialize_String_vector (zookeeper.jute.c:245)
==11674== by 0xC842F9: deserialize_GetChildrenResponse (zookeeper.jute.c:874)
==11674== by 0xC7E9F0: zookeeper_process (zookeeper.c:1904)
==11674== by 0xC7FE5B: do_io (mt_adaptor.c:439)
==11674== by 0x4E39E99: start_thread (pthread_create.c:308)
==11674== by 0x5FA6DBC: clone (clone.S:112)
Attachments
Issue Links
- is related to
-
ZOOKEEPER-1632 fix memory leaks in cli_st
- Closed
- relates to
-
ZOOKEEPER-2015 I found memory leak in zk client for c++
- Resolved