Hello, quick reminder for the plans to release v5.4.1 tomorrow, just in case someone has encountered any (potential) issue in the 5.4 branch and it is not reported, do it so we can have a look and maybe it can be fixed in time for the patch release. Cheers, Daniel

That's indeed on shutdown, depending on what the server is doing at that time, some races may still happen. Do you get it every time? Anyhow, a full trace would be good to have, the crash is anyhow inside libssl, but can be because of shared memory being released... Cheers, Daniel On 01.09.20 01:24, Anthony Joseph Messina wrote: > On Monday, August 31, 2020 9:52:06 AM CDT Daniel-Constantin Mierla wrote: >> Hello, >> >> quick reminder for the plans to release v5.4.1 tomorrow, just in case >> someone has encountered any (potential) issue in the 5.4 branch and it >> is not reported, do it so we can have a look and maybe it can be fixed >> in time for the patch release. >> >> Cheers, >> Daniel > > I've run into the following crash on exit using Kamailio built using the > 5.4 branch up to e9baba91c6. > > I haven't had time to do a full trace or investigate more deeply as we're > quite busy at work.> > Stack trace of thread 191257: > #0 0x00007f3203393056 ossl_init_thread_stop > (libcrypto.so.1.1 + 0x186056) > #1 0x00007f320339335f OPENSSL_cleanup (libcrypto.so.1.1 + > 0x18635f) > #2 0x00007f32041013a7 __run_exit_handlers (libc.so.6 + > 0x3f3a7) > #3 0x00007f3204101550 exit (libc.so.6 + 0x3f550) > #4 0x000000000041f61a handle_sigs (kamailio + 0x1f61a) > #5 0x000000000042c61c main_loop (kamailio + 0x2c61c) > #6 0x0000000000434cbd main (kamailio + 0x34cbd) > #7 0x00007f32040e9042 __libc_start_main (libc.so.6 + > 0x27042) > #8 0x000000000041bbde _start (kamailio + 0x1bbde)