Re: [OpenSIPS-Users] Potential memory leak in siptrace module

2018-02-02 Thread Răzvan Crainea
;, "trace_id", "[tid]uri=mysql://db-user:db-pass@db-host/db-name;table=sip_trace;") *From:*Bogdan-Andrei Iancu [mailto:bog...@opensips.org] *Sent:* Thursday, February 1, 2018 10:54 AM *To:* OpenSIPS users mailling list <users@lists.opensips.org>; Steve Brisson <steve.br

Re: [OpenSIPS-Users] Potential memory leak in siptrace module

2018-02-01 Thread Steve Brisson
uot;trace_id", "[tid]uri=mysql://db-user:db-pass@db-host/db-name;table=sip_trace;") From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Thursday, February 1, 2018 10:54 AM To: OpenSIPS users mailling list <users@lists.opensips.org>; Steve Brisson <steve.bris...@li

Re: [OpenSIPS-Users] Potential memory leak in siptrace module

2018-02-01 Thread Bogdan-Andrei Iancu
Hi Steve, Thank you for your report. Could you provide the exact revision of your OpenSIPS (opensips -V) ? Also what requests are you calling the sip_trace() for (INVITES ? PUBLISH? all?) and what are the input paramters ? Thanks, Bogdan-Andrei Iancu OpenSIPS Founder and Developer

[OpenSIPS-Users] Potential memory leak in siptrace module

2018-01-31 Thread Steve Brisson
I've found that when I call the sip_trace method, in the main request routing block, the shmem used_size and fragments continually increases until the process crashes from an out of memory condition. By enabling memory alloc debugging, I confirmed that the leaked allocation is the shm_malloc