OK, got the logs and found the double free:
Sep 23 15:24:24 lohi /usr/bin/sip-proxy[13512]: WARNING: tm [h_table.c:126]: free_cell_helper(): ===== freeing transaction 0x7f70387e6470 from timer.c:648
Sep 23 15:25:31 lohi /usr/bin/sip-proxy[13512]: WARNING: tm [h_table.c:126]: free_cell_helper(): ===== freeing transaction 0x7f70387e6470 from timer.c:648
I will try to figure out why timer gets fired two times for these free, it is more than 1min in between.
Daniel
On 23/09/15 14:48, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Can you send the log messages with:
===== freeing transaction
below, juha
On Wednesday 23 September 2015, Daniel-Constantin Mierla wrote:
OK, got the logs and found the double free:
Sep 23 15:24:24 lohi /usr/bin/sip-proxy[13512]: WARNING: tm [h_table.c:126]: free_cell_helper(): ===== freeing transaction 0x7f70387e6470 from timer.c:648
Sep 23 15:25:31 lohi /usr/bin/sip-proxy[13512]: WARNING: tm [h_table.c:126]: free_cell_helper(): ===== freeing transaction 0x7f70387e6470 from timer.c:648
I will try to figure out why timer gets fired two times for these free, it is more than 1min in between.
Beware, these might be 2 separate transactions. It is not uncommon for a transaction to get the same memory chunk assigned as a freed previous transaction. The log should probably also mention every creation of a new transaction, not just the destruction.
-
Alex Hermann -
Daniel-Constantin Mierla