Hi Liviu,
I did a quick look myself at dlg_timer.c (around the lines that crash
happens) and there is actually a FIXME note there too. it seems to me that
this issue happens when using create_dialog("PpB"), if one side is already
disconnected and also PpB doesn't receive a ping and decides to disconnect
the call, the module crashes. Basically, if the call is already
disconnected, we should not try to send BYE to them either.
For now, I removed "PpB" from create_dialog and the error has not occurred
again. I think that can be the workaround for now.Thanks, Mark On Wed, Nov 11, 2020 at 3:40 PM Liviu Chircu <[email protected]> wrote: > On 07.11.2020 13:27, M S wrote: > > The server has a pretty high load, is Q_MALLOC_DBG safe? > > How "pretty" high of a load is that, in terms of "calls-per-second" and > "max-concurrent-calls"? Q_MALLOC_DBG will typically add +30-50% to > shared/private memory usage, as well as maybe a 10% increase in CPU > usage. But OpenSIPS uses very few CPU and memory to begin with, so it > will be quite safe to do. > > My advice: unless you're running more than 50 calls-per-second through > it, there is no need to even start worrying about Q_MALLOC_DBG altering > the system's behavior. Below the 50 CPS level, the difference is > unnoticeable. > > > also, is that an opensips command-line option? I don't see it in the > > opensips man page... > Yes, it's a "opensips" binary command-line option. The man page needs > updating, indeed, however you could try "opensips -h" and you'll see > that option. > > -- > Liviu Chircu > www.twitter.com/liviuchircu | www.opensips-solutions.com > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
