Hide Forgot
Description of problem: Any run of qpid-config tool causes a small memory consumption increase of qpidd process. Version-Release number of selected component (if applicable): MRG(M) 1.3 How reproducible: Every time running reproduction steps. Steps to Reproduce: 1. Start qpidd service with any configuration (i.e. default qpidd.conf). 2. Run in a loop qpid-config with any argument(s). Some examples are below. 3. Monitor qpidd process (physical) memory usage - it will slowly grow. Actual results: Examples to step 2: (*) for i in $(seq 1 100); do qpid-config; sleep 5; done (*) for i in $(seq 1 100); do qpid-config queues; sleep 5; done (*) for i in $(seq 1 100); do qpid-config queues -b; sleep 5; done (*) for i in $(seq 1 100); do qpid-config exchanges; sleep 5; done (*) for i in $(seq 1 100); do qpid-config exchanges -b; sleep 5; done (*) for i in $(seq 1 50); do qpid-config add queue some_name; sleep 5; qpid-config del queue some_name; sleep 5; done (*) for i in $(seq 1 50); do qpid-config add exchange topic some_name; sleep 5; qpid-config del exchange some_name; sleep 5; done In all such cases, the 100 runs of qpid-config tool increased memory usage by approx. 1MB, i.e. 1 run of the tool consumes around 10kB. Expected results: No memory consumption grow should occur. As e.g. qpid-config tool can be used to regularly monitoring of QPid status, memory consumption would be steadily growing forever. Additional info:
I left infinite loop running qpid-config command to be run for several days and at the end the memory utilisation stabilised on 83m of RES memory - and it is not further growing for >24 hours. Anyway, why the physical memory usage has increased from 7MB to 83MB?
The test continued further and memory usage started to grow again..
Re-tested it on qpid-cpp-server-0.10-9.el5 even with MALLOC_MMAP_THRESHOLD_=8 to prevent memory fragmentation and the mem.leak is still there: both VSZ and RSS is increasing.
Closing as duplicate of bz 729441 / JIRA 3403 (verified by myself). *** This bug has been marked as a duplicate of bug 729441 ***