|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Valgrind showing MEMORY LEAKS on libmqm.so? |
« View previous topic :: View next topic » |
Author |
Message
|
lyntongrice |
Posted: Sun Dec 04, 2011 1:26 am Post subject: Valgrind showing MEMORY LEAKS on libmqm.so? |
|
|
Acolyte
Joined: 26 Sep 2010 Posts: 70
|
Hi there,
I have an application written in C that is running on AIX, Solaris and Linux. I seem to have a small memory leak and am trying to track it down..
I have run Valgrind on Linux and get the following after running Valgrind.
==12811== LEAK SUMMARY:
==12811== definitely lost: 70,794 bytes in 11 blocks
==12811== indirectly lost: 0 bytes in 0 blocks
==12811== possibly lost: 69,960 bytes in 19 blocks
==12811== still reachable: 61,795 bytes in 133 blocks
==12811== suppressed: 0 bytes in 0 blocks
Now I am not worried about the "definetly lost" or "possibly lost", but more the "still reachable" as that is the ONLY one that continues to grow.
I use both the SAP and IBM libs for the application and see that IBM does add to the "still reachable", so for example:
==12811== 8,560 bytes in 1 blocks are still reachable in loss record 42 of 48
==12811== at 0x4A067BA: malloc (vg_replace_malloc.c:263)
==12811== by 0x65381C9: InitPrivateServices (in /opt/mqm/lib64/libmqmcs.so)
==12811== by 0x653A160: xcsInitializeEx (in /opt/mqm/lib64/libmqmcs.so)
==12811== by 0x6259B1E: zstInitCS (in /opt/mqm/lib64/libmqz.so)
==12811== by 0x624EA09: zstMQConnect (in /opt/mqm/lib64/libmqz.so)
==12811== by 0x6250BFA: zstMQCONNX (in /opt/mqm/lib64/libmqz.so)
==12811== by 0x60B1605: MQCONNX (in /opt/mqm/lib64/libmqm.so)
==12811== by 0x585CEBA: receiver_initialize (receiver.c:1
==12811== by 0x4E10D58: receiver_proxy_initialize (receiver_proxy.c:17)
==12811== by 0x402D02: initialiseWMQReceiverProxy (outbound.c:296)
==12811== by 0x4027E8: outboundThreadMainLoop (ioutbound.c:209)
==12811== by 0x37EA2077E0: start_thread (in /lib64/libpthread-2.12.so)
And again (occurs numerous times):
==12811== 4,000 bytes in 1 blocks are still reachable in loss record 37 of 48
==12811== at 0x4A067BA: malloc (vg_replace_malloc.c:263)
==12811== by 0x656F19A: xppInitialize (in /opt/mqm/lib64/libmqmcs.so)
==12811== by 0x6538802: InitProcessInitialisation (in /opt/mqm/lib64/libmqmcs.so)
==12811== by 0x653A3D4: xcsInitializeEx (in /opt/mqm/lib64/libmqmcs.so)
==12811== by 0x653AF94: xcsInitialize (in /opt/mqm/lib64/libmqmcs.so)
==12811== by 0x6250BAC: zstMQCONNX (in /opt/mqm/lib64/libmqz.so)
==12811== by 0x60B1605: MQCONNX (in /opt/mqm/lib64/libmqm.so)
==12811== by 0x585CEBA: wmq_receiver_initialize (receiver.c:1
==12811== by 0x4E10D58: wmq_receiver_proxy_initialize (receiver_proxy.c:17)
==12811== by 0x402D02: initialiseWMQReceiverProxy (outbound.c:296)
==12811== by 0x4027E8: outboundThreadMainLoop (outbound.c:209)
==12811== by 0x37EA2077E0: start_thread (in /lib64/libpthread-2.12.so)
Just curious is you think I need to be worried about this? I must admit that I have way more issues with the SAP libs, but overall both are contributing to increased memory growth in the application...
Thanks for the help
Lynton |
|
Back to top |
|
 |
mqjeff |
Posted: Sun Dec 04, 2011 6:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
If you believe you have identified a leak that occurs inside the IBM libraries, then you need to open a PMR.
Otherwise, you need to show the code you have written that calls the IBM libraries. |
|
Back to top |
|
 |
Vitor |
Posted: Sun Dec 04, 2011 7:28 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
If you believe you have identified a leak that occurs inside the IBM libraries, then you need to open a PMR. |
Even if you're right and the IBM code is leaking, there's nothing we're going to do that'll be much use. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|