[JDEV] Memory leak, bug -- Help

Glenn MacGregor gtm at oracom.com
Mon Apr 1 08:49:20 CST 2002


Hi All,

I have been testing the jabber 1.4.2 server for some time, I think I may
have found a memory leak or a logic bug somewhere in the deliver stuff.

The setup is standard 1.4.2 server compiled on a redhat 7.1 box with
gcc3.0.4.
Jabber TestSuite from sf.net

Jabber configuration changes:
    take out offline storage in the jsm section.
    turn off karma in the c2s section of jabber.xml

Then run  jabberd/jabberd/ -h hostname
>From the testsuite run the msgloadrec -h hostname -t username1 -d
then run msgloadsnd -h hostname -t username1 -f  username2 -m 5000

msgloadrec will wait to receive messages as user: username1
msgloadsnd will send -m messages from user: username2 to user: username1 as
fast as it can.  --throttle-secs and --throttle-usecs will throttle the
sending of messages.

You can now watch a top of jabberd and see that about every 100 messages or
so the memory increases by 4K.

You will see the same results if you send one message a second (it just
takes longer), so it doesn't seem to be a throughput problem in the jabber
server.

I have been looking at this for about a week now and am not getting too far.
Any help would be great.

I would say that this is a fairly large problem, because at some point the
server will need to be restarted.


    Thanks

            Glenn






More information about the JDev mailing list