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
and doing the same test never results in failure. I used -m 64 -M 2 options to test on a system not taking any calls just to narrow down the problem. I tried looking into the code to see if I could spot where it was missing when a TLS connection fails, but it is a bit more involved than I can spend right now.
Expected behavior
TLS connection failures should cleanup memory used by HEP(speculation) just like successful connection end.
Relevant System Logs
Provided above.
OS/environment information
Debian 12
Opensips installed from Opensips package installation process provided by Opensips.org
Additional context
The TLS errors are high on our network as there is a LoadBalancer that makes a TCP connection to the port to validate reachability. It is currently not capable of negotiating TLS. This was not a problem for 2.4 version of Opensips.
The text was updated successfully, but these errors were encountered:
zooptwopointone
changed the title
Memory leak in TLS connection ERROR when HEP is enabled for TLS
[Bug] Memory leak in TLS connection ERROR when HEP is enabled for TLS
Oct 17, 2024
zooptwopointone
changed the title
[Bug] Memory leak in TLS connection ERROR when HEP is enabled for TLS
[BUG] Memory leak in TLS connection ERROR when HEP is enabled for TLS
Oct 17, 2024
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days.
OpenSIPS version you are running
Describe the bug
There appears to be a Memory leak in PKG memory for TLS connections when HEP is enabled for TLS.
To Reproduce
Using Wolf SSL
Running this in a loop, which connects sends nothing over and closes the connection. So that TLS fails.
Will result in this error message, which also starts to cause problems with real calls.
Commenting out
and doing the same test never results in failure. I used -m 64 -M 2 options to test on a system not taking any calls just to narrow down the problem. I tried looking into the code to see if I could spot where it was missing when a TLS connection fails, but it is a bit more involved than I can spend right now.
Expected behavior
TLS connection failures should cleanup memory used by HEP(speculation) just like successful connection end.
Relevant System Logs
Provided above.
OS/environment information
Debian 12
Opensips installed from Opensips package installation process provided by Opensips.org
Additional context
The TLS errors are high on our network as there is a LoadBalancer that makes a TCP connection to the port to validate reachability. It is currently not capable of negotiating TLS. This was not a problem for 2.4 version of Opensips.
The text was updated successfully, but these errors were encountered: