The problem actually occured after we added the CRL some weeks ago.. without
CRL there was no such behaviour.
And of course there are a lot options to mitigate the issue respectively
decrease the propability by doing less reloads by decreasing the cycle and/or
check if there was a change at the CRL at all..
Anyhow i thought raising an issue makes sense, because from my point of view
there is definitively some memory leaking when using tls.reload in combination
with a CRL..
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3823#issuecomment-2099786134
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3823/2099786...@github.com>
_______________________________________________
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
