[Users] memory leak in presence module?

[Klaus Darilion]

Hi Daniel!

I've tried with t_release and it was running fine several hours without 
leaking. But then, unfortunately openser terminated with signal 9. I've 
never seen this before. Do you know what this means?

The log (see below) is strange because before signal 9 there were 5 
minutes without log messages although sipp was constantly sending 
traffic to openser. Thus, I guess something inside openser blocked and 
then it was terminated - but who terminated openser? Who sent signal 9?

There was no core generated (although DUMP_CORE=yes), maybe signal 9 
doesn't cause a core to be generated?

regards
klaus

Apr 26 20:37:56 ds3000 /usr/sbin/openser[32212]: 
32b24f15e52d603ba890a9729723c4b0.6319///46-29299 at 83.136.32.132 PUBLISH 
detected, handle_publish ... outside t_newtran
Apr 26 20:37:56 ds3000 /usr/sbin/openser[32214]: 
32b24f15e52d603ba890a9729723c4b0.c7af///33-29299 at 83.136.32.132 PUBLISH 
detected, handle_publish ... outside t_newtran
Apr 26 20:37:56 ds3000 /usr/sbin/openser[32208]: 
32b24f15e52d603ba890a9729723c4b0.7875///36-29299 at 83.136.32.132 PUBLISH 
detected, handle_publish ... outside t_newtran
Apr 26 20:37:57 ds3000 /usr/sbin/openser[32214]: 
32b24f15e52d603ba890a9729723c4b0.c7af///33-29299 at 83.136.32.132 PUBLISH 
detected, handle_publish ... inside t_newtran
Apr 26 20:37:57 ds3000 /usr/sbin/openser[32208]: 
32b24f15e52d603ba890a9729723c4b0.7875///36-29299 at 83.136.32.132 PUBLISH 
detected, handle_publish ... inside t_newtran
Apr 26 20:37:57 ds3000 /usr/sbin/openser[32212]: 
32b24f15e52d603ba890a9729723c4b0.6319///46-29299 at 83.136.32.132 PUBLISH 
detected, handle_publish ... inside t_newtran
Apr 26 20:37:57 ds3000 /usr/sbin/openser[32210]: 
32b24f15e52d603ba890a9729723c4b0.8d38///5-29299 at 83.136.32.132 PUBLISH 
detected, handle_publish ... inside t_newtran
Apr 26 20:42:53 ds3000 /usr/sbin/openser[32204]: child process 32208 
exited by a signal 9
Apr 26 20:43:00 ds3000 /usr/sbin/openser[32204]: core was not generated
Apr 26 20:43:00 ds3000 /usr/sbin/openser[32204]: INFO: terminating due 
to SIGCHLD
Apr 26 20:43:00 ds3000 /usr/sbin/openser[32214]: INFO: signal 15 received
Apr 26 20:43:00 ds3000 /usr/sbin/openser[32214]: Memory status (pkg):
Apr 26 20:43:00 ds3000 /usr/sbin/openser[32216]: INFO: signal 15 received
Apr 26 20:43:00 ds3000 /usr/sbin/openser[32216]: Memory status (pkg):
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32226]: INFO: signal 15 received
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32226]: Memory status (pkg):
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32212]: INFO: signal 15 received
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32218]: INFO: signal 15 received
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32224]: INFO: signal 15 received
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32220]: INFO: signal 15 received
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32222]: INFO: signal 15 received
Apr 26 20:43:06 ds3000 /usr/sbin/openser[32210]: INFO: signal 15 received