Open shahrukh330 opened 7 years ago
are you running on more than one core ? Have you enabled more than one core for licode?
why do you think this is a deadlock?
@jcague maybe iam wrong but a quick search about __lll_lock_wait tells me its a deadlock. This is a rare case and comes when users are consistently joining and exiting a room.
IMO it's just a mutex inside libnice, but it could be a deadlock if multiple threads are stuck at the same mutex and they don't advance. Can you test if that thread remains waiting the same lock please?
@jcague I ll try to reproduce and let you know.
Hi,
I think i found a deadlock, I am attaching stacktrace as follows. It occurs when there are more then 12 users in the room and all try to join simultaneously.
__lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 135 in ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S (gdb) backtrace
0 __lll_lock_wait ()
1 0x00007fd1ed9b668d in _L_lock_1082 ()
from /lib/x86_64-linux-gnu/libpthread.so.0
2 0x00007fd1ed9b6607 in __GI___pthread_mutex_lock (mutex=0x3fbb9c0)
3 0x00007fd1ea71c981 in g_mutex_lock ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
4 0x00007fd1e9df5aec in agent_lock () at agent.c:139
5 0x00007fd1e9df5b9c in nice_agent_set_property (object=0x7b1ade0,
6 0x00007fd1ea4596e3 in g_object_set_property ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
7 0x00007fd1ead47014 in erizo::NiceConnection::start (this=0x7b19040)
8 0x00007fd1ead26931 in erizo::DtlsTransport::start (this=0x7b17520)
9 0x00007fd1ead7e7c6 in erizo::WebRtcConnection::setRemoteSdp (