Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.11.0
-
None
Description
It seems that binary protocol has memory leaks, it's loosing few bytes per request.
==4534== 2,399,952 bytes in 99,998 blocks are definitely lost in loss record 611 of 611
==4534== at 0x4C2FB25: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==4534== by 0x5300580: g_malloc0 (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5306.0)
==4534== by 0x4E49774: thrift_binary_protocol_read_string (thrift_binary_protocol.c:797)
==4534== by 0x4E48E55: thrift_binary_protocol_read_message_begin (thrift_binary_protocol.c:431)
==4534== by 0x4E46013: thrift_multiplexed_processor_process_impl (thrift_multiplexed_processor.c:60)
==4534== by 0x4E51864: thrift_simple_server_serve (thrift_simple_server.c:58)
==4534== by 0x108DAF: test_server_initialize (test_server.c:74)
==4534== by 0x5321459: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5306.0)
==4534== by 0x532138A: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5306.0)
==4534== by 0x5321631: g_test_run_suite (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.5306.0)
I'm testing on trunk master so will fix it there.