[Pidgin] #3725: Memory leak in jabber presence parsing

[Pidgin]

#3725: Memory leak in jabber presence parsing
-----------------------------------------+----------------------------------
 Reporter:  praveen                      |       Type:  defect
   Status:  new                          |   Priority:  minor 
Component:  libpurple                    |    Version:  2.2.2 
 Keywords:  jabber memory leak presence  |    Pending:  0     
-----------------------------------------+----------------------------------
 There seems to be a memory leak everytime jabber receives presence info.
 Memory is allocated for parsing the xml node, but never released
 (jabber/presence.c:726). Here is a section from valgrind output.


 ==6081== 6,753 bytes in 232 blocks are definitely lost in loss record 30
 of 37

 ==6081==    at 0x401C422: malloc (vg_replace_malloc.c:149)

 ==6081==    by 0x427A041: g_malloc (in /usr/lib/libglib-2.0.so.0.1000.3)

 ==6081==    by 0x4289D95: g_strdup (in /usr/lib/libglib-2.0.so.0.1000.3)

 ==6081==    by 0x4792D83: jabber_presence_parse (presence.c:726)

 ==6081==    by 0x478D232: jabber_process_packet (jabber.c:199)

 ==6081==    by 0x4791420: jabber_parser_element_end_libxml (parser.c:116)

 ==6081==    by 0x4309292: (within /usr/lib/libxml2.so.2.6.24)

 ==6081==    by 0x4311472: xmlParseChunk (in /usr/lib/libxml2.so.2.6.24)

 ==6081==    by 0x479152C: jabber_parser_process (parser.c:195)

 ==6081==    by 0x4786577: jabber_recv_cb_ssl (jabber.c:400)

 ==6081==    by 0x407C9B8: recv_cb (sslconn.c:143)

-- 
Ticket URL: <http://developer.pidgin.im/ticket/3725>
Pidgin <http://pidgin.im>
Pidgin