Please post some crash logs, a backtrace, or anything that might be useful in making progress with this. For example, you could do 200 calls, print out the memory status with SIGUSR1 [1] and post it here. Or you could post some pre-crash logs. Or post-crash.

[1]: http://www.opensips.org/Documentation/TroubleShooting-OutOfMem

Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com

On 24.07.2017 11:28, Evgeniy G. via Users wrote:
Hi, Liviu Chircu
I found out the memory stick when Opensips fell. I measured the average
memory usage value by one call of 0.064MB. Then, at startup, Opensips
indicated using 32M of shared memory. Using the values from the statistics
(shmem: free_size 29996944 B) translated it into MB (28,6073). The result
was divided by 0,064 resulting in about 447 calls. And then the magic begins
=).
After 448 calls, OpenSIPs crashes. Similarly, it happens when you specify a
memory of more than 32MB.
I use the Opencips on CentOS 7. I did not observe such a problem on Ubuntu
16.04 TLS.



--
View this message in context: 
http://opensips-open-sip-server.1449251.n2.nabble.com/Does-not-release-shared-memory-tp7608065p7608080.html
Sent from the OpenSIPS - Users mailing list archive at Nabble.com.

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to