Hi, we're running sipp in server mode in the background for testing purposes, and noticed that it gobbles up insane amounts of memory in the long run. Running under Valgrind produced the following leak report:
450,912 bytes in 1,281 blocks are possibly lost in loss record 35 of 37
at 0x402377E: operator new(unsigned) (vg_replace_malloc.c:224)
by 0x8073122: process_message(sipp_socket*, char*, int, sockaddr_storage*) (in /usr/bin/sipp)
by 0x8079243: pollset_process(int) (in /usr/bin/sipp)
by 0x8079819: traffic_thread() (in /usr/bin/sipp)
by 0x807CF9F: main (in /usr/bin/sipp)
which hinted that incoming call objects are leaking. Interestingly, addig -d 1 to the sipp server command line removed the leak.
We're using a basic UAS responder scenario under sipp SVN revision 599.
Log in to post a comment.