You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the coredump at On was able to trace the SIGSEGV *happening in the
garbage collector thread* that the UDT library starts (!):
6 0x000055e8617dd78e in CSndBuffer::~CSndBuffer (this=0x7f8e7c0021a0, __in_chrg=<optimized out>) at /usr/local/src/jive5ab.git/libudt5ab/buffer.cpp:101
7 0x000055e8617e208b in CUDT::~CUDT (this=0x55e8652c9780, __in_chrg=<optimized out>) at /usr/local/src/jive5ab.git/libudt5ab/core.cpp:195
8 0x000055e8617cab58 in CUDTSocket::~CUDTSocket (this=0x55e8652c9650, __in_chrg=<optimized out>) at /usr/local/src/jive5ab.git/libudt5ab/api.cpp:99
so it's likely that ~CSndBuffer() is being executed from different
threads and the d'tor has no protection at all against that.
It's a probable cause for sigsegv'ing so added a mutex (on non-Win32
systems) to see if that fixes the issue reported
0 commit comments