[THRIFT-3552] glib_c Memory Leak

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 0.9.3
• Fix Version/s: 0.10.0
• Component/s: C glib - Library
• Patch Info: Patch Available
• Assignee: Simon South
• Reporter: Anish Shah
• Created: 13/Jan/16 19:47
• Updated: 19/Feb/16 02:17
• Resolved: 16/Jan/16 12:10

Description

I have been seeing some memory leaks using valgring in my testprogram.

Leak:

==94320== 17,878 bytes in 2,712 blocks are definitely lost in loss record 987 of 1,018
==94320== at 0x4A057BB: calloc (vg_replace_malloc.c:593)
==94320== by 0x3D7DA49BF7: g_malloc0 (gmem.c:196)
==94320== by 0x5768002: thrift_binary_protocol_read_string (thrift_binary_protocol.c:791)
==94320== by 0x5768987: thrift_binary_protocol_read_message_begin (thrift_binary_protocol.c:431)
==94320== by 0x576702E: thrift_dispatch_processor_process (thrift_dispatch_processor.c:41)
==94320== by 0x576CC06: thrift_simple_server_serve (thrift_simple_server.c:62)
==94320== by 0x45A548: server_start (server.c:135)
==94320== by 0x3D7C607A50: start_thread (pthread_create.c:301)
==94320== by 0x3D7C2E893C: clone (clone.S:115)

My question is where is the *str memory allocated by function thrift_binary_protocol_read_string() freed? Am I doing something wrong or is there an actual memory leak?