Memleak when re-connecting a Jardin Client

Bug #507107 reported by Aleksander Morgado
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
El Jardin
Fix Released
High
Aleksander Morgado

Bug Description

When for example jardin_client_send_receive() gives a timeout, re-connection try happens automatically in the Jardin client, so it will actually disconnect() the connection module, and connect() the connection module again.

The problem is that when 2nd connect() in the same connection module happens, jardin_connection_module_socket() is called again, and both _host_address and _peer_address struct address-es are re-allocated again, without deallocating them previously.

The fix could be just:
 * If already allocated, just memset() them to 0

Changed in eljardin:
milestone: none → 2.0.2005
importance: Undecided → High
assignee: nobody → Aleksander Morgado (aleksander-m)
status: New → Confirmed
Revision history for this message
Aleksander Morgado (aleksander-m) wrote :

Fixed in trunk now.

Changed in eljardin:
status: Confirmed → Fix Committed
Changed in eljardin:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.