Hi Razvan, Let me enable it and wait for the next crash.
Regards, -- Ahsan Hasan On Thu, Jan 9, 2014 at 12:44 PM, Răzvan Crainea <raz...@opensips.org> wrote: > Hi, Ahsan! > > Can you please enable the the memory debugging (DBG_QM_MALLOC flag in > menuconfig)? You can follow this tutorial[1]. > > [1] http://www.opensips.org/Documentation/TroubleShooting-OutOfMem > > Best regards, > > Razvan Crainea > OpenSIPS Core Developer > http://www.opensips-solutions.com > > > On 01/09/2014 07:54 AM, Ahsan Hasan wrote: > >> >> We are using opensips-1.9.1 and it is crashing randomly every other >> week, the core dumps generated are always related to memory leakage. The >> last four core dumps are >> >> Program terminated with signal 11, Segmentation fault. >> #0 0x00007f4c12e20c77 in write_dialog_profiles (links=0x7f4bff03d7f0) >> at dlg_db_handler.c:1085 >> 1085 l += link->profile->name.len + 1 + link->value.len + 1; >> >> Program terminated with signal 11, Segmentation fault. >> #0 0x00000000004e5da2 in fm_remove_free (qm=0x7f4bfec5a000, size=112) >> at mem/f_malloc.c:172 >> 172 *pf=n->u.nxt_free; >> >> Program terminated with signal 11, Segmentation fault. >> #0 free_cloned_sdp_session (_session=0x362e373740333532) at >> parser/sdp/sdp.c:893 >> 893 session = l_session->next; >> >> Program terminated with signal 11, Segmentation fault. >> #0 0x00000000004e5da2 in fm_remove_free (qm=0x7f71a9524000, size=96) at >> mem/f_malloc.c:172 >> 172 *pf=n->u.nxt_free; >> >> What can be the cause? >> >> -- >> Ahsan Hasan >> >> >> >> _______________________________________________ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users