It could be. i'ld suggest upgrading SER so that you don't hunt historical errors
and then
following memory-problem-reporting guidelines (a bit tedious but provides the so needed
info about what's wrong). For that, SER needs to be run for a while so that the
syslog
shows execsively frequentlya allcated fragments which haven't been freed.
-jiri
At 09:41 11/10/2007, Zappasodi Daniele wrote:
Hello,
I need help to interpret the syslog.
I have a problem with memory, maybe there is memory leak: after few hours and few cps, my
ser goes out of memory
Feb 8 17:27:29 SAM-IP ser[2193]: ERROR: sip_msg_cloner: cannot allocate memory
Feb 8 17:27:29 SAM-IP ser[2193]: ERROR: new_t: out of mem:
Feb 8 17:27:29 SAM-IP ser[2193]: ERROR: t_newtran: new_t failed
If I stop the test and I wait, ser doesn't release memory and it continues to refuse
every call with "out of mem".
I have attached the end of the syslog (ser recompiled with DBG_QM_MALLOC options).
I don't understand if the messages in this trace contain info about a memory leak, but
if I stop ser immediately after the start without any call, I don't see great
differences in the syslog.
I'm using ser 0.9.6.
What else can I do to search more info about memory leak?
Thanks,
Zappasodi Daniele
**********************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this message
by anyone else is unauthorized. If you are not the intended recipient, any
disclosure, copying, or distribution of the message, or any action or
omission taken by you in reliance on it, is prohibited and may be unlawful.
Please immediately contact the sender if you have received this message inerror.
**********************************************************************
_______________________________________________
Serusers mailing list
Serusers@lists.iptel.orghttp://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan
http://iptel.org/~jiri/