dan clark created QPID-8134:
-------------------------------
Summary: qpid::client::amqp0_10::SenderImpl::sendImpl multiple
memory leaks
Key: QPID-8134
URL: https://issues.apache.org/jira/browse/QPID-8134
Project: Qpid
Issue Type: Bug
Components: C++ Client
Affects Versions: qpid-cpp-1.37.0
Environment: *CentOS* Linux release 7.4.1708 (Core)
Linux localhost.novalocal 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC
2015 x86_64 x86_64 x86_64 GNU/Linux
*qpid*-qmf-1.37.0-1.el7.x86_64
*qpid*-dispatch-debuginfo-1.0.0-1.el7.x86_64
python-*qpid*-1.37.0-1.el7.noarch
*qpid*-proton-c-0.18.1-1.el7.x86_64
python-*qpid*-qmf-1.37.0-1.el7.x86_64
*qpid*-proton-debuginfo-0.18.1-1.el7.x86_64
*qpid*-cpp-debuginfo-1.37.0-1.el7.x86_64
*qpid*-cpp-client-devel-1.37.0-1.el7.x86_64
*qpid*-cpp-server-1.37.0-1.el7.x86_64
*qpid*-cpp-client-1.37.0-1.el7.x86_64
Reporter: dan clark
Attachments: drain.cpp, godrain.sh, gospout.sh, qpid-stat.out,
spout.cpp, spout.log
There may be multiple leaks of the outgoing message structure and associated
fields when using the qpid::client::amqp0_10::SenderImpl::send function to
publish messages under certain setups. I will concede that there may be options
that are beyond my ken to ameliorate the messages, especially since there is an
indication that under prolonged longs (a demonized version of an application
like spout) that the statistics for quidd indicate increased acquires with zero
releases.
Capturing the leaks using the test applications spout required adding an
'exit()' prior to the close, as during normal operations of a daemon, the
connection remains open for a sustained period of time, thus the leak of
structures within the c++ client library are found as structures still tracked
by the library and cleaned up on exit, but they should be cleaned up as a
result of the completion of the send or the termination of the TTL of the
message which ever comes first. I have witnessed growth of the leaked
structures into the millions of messages based on scenarios attached using
spout/drain as test vehicle.
The attached log uses a short 10message test and the spout.log contains 5 sets
of different structures leaked (found with the 'bytes in 10 blocks are still
reachable' lines.)
The leaks seem to be associated with structures allocation 'strings' to save
the "subject" and the "payload" for string based messages send for amq.topic
output.
Suggested work arounds are welcome for application level fixes to spout/drain
(if they are missing key components) or changes to the address/setup of the
queues for amq.topic messages.
For example:
==3388== 3,680 bytes in 10 blocks are still reachable in loss record 233 of 234
==3388== at 0x4C2A203: operator new(unsigned long) (vg_replace_malloc.c:334)
==3388== by 0x4EB046C: qpid::client::Message::Message(std::string const&,
std::string const&) (Message.cpp:31)
==3388== by 0x51742C1:
qpid::client::amqp0_10::OutgoingMessage::OutgoingMessage()
(OutgoingMessage.cpp:167)
==3388== by 0x5186200:
qpid::client::amqp0_10::SenderImpl::sendImpl(qpid::messaging::Message const&)
(SenderImpl.cpp:140)
==3388== by 0x5186485: operator() (SenderImpl.h:114)
==3388== by 0x5186485: execute<qpid::client::amqp0_10::SenderImpl::Send>
(SessionImpl.h:102)
==3388== by 0x5186485:
qpid::client::amqp0_10::SenderImpl::send(qpid::messaging::Message const&, bool)
(SenderImpl.cpp:49)
==3388== by 0x40438D: main (spout.cpp:185)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
