Hi,
shared memory not freed once TLS connection close means shm available
memory decreasing for new connection that leads to the following error
*tls: ssl bug #1491 workaround: not enough memory for safe operation*
*TestCase:*
1. start kamailio
2. use sample program to establish tls connection and close imediately.
3. Kamailio Log is
For first TLS connection
tls [tls_server.c:189]: tls_complete_init(): tls: enough memory for
safe operation: shm=63604096 threshold1=12058624
tls [tls_server.c:649]: tls_h_tcpconn_clean(): tls shm_available after
shm_free: 63545192
For second TLS connection
tls [tls_server.c:189]: tls_complete_init(): tls: enough memory for
safe operation: shm=63545192 threshold1=12058624
tls [tls_server.c:649]: tls_h_tcpconn_clean(): tls shm_available after
shm_free: 63489352
*Memory Leak:*
for tls connection connection
63604096 - 63545192 = 58904 bytes not freed.
for tls connection connection
63545192 - 63489352 = 55840 bytes not freed.
I tested same scenario on kamailio - 4.2.4, 4.3.4 versions result is same.
Could you please provide the fix?
Thanks & Regards,
Raja Chegondi.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
