activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Timothy Bish <tabish...@gmail.com>
Subject Re: activemq-cpp-library-3.8.2 memory leak
Date Thu, 07 Aug 2014 10:13:10 GMT
On 08/07/2014 01:03 AM, Suresh Bollabathula wrote:
> Hi
>
> I am seeing following memory leak with activemq-cms-3.8.2 consistently.
>
> ==7369== 2,604 (48 direct, 2,556 indirect) bytes in 1 blocks are definitely
> lost in loss record 1,819 of 2,022
> ==7369==    at 0x4A084CC: operator new(unsigned long)
> (vg_replace_malloc.c:298)
> ==7369==    by 0xF9CD8A1: decaf::util::concurrent::Future<bool>*
> decaf::util::concurrent::ExecutorService::submit<bool>(decaf::lang::Runnable*,
> bool const&, bool) (FutureTask.h:408)
> ==7369==    by 0xF9B9CBB:
> activemq::core::kernels::ActiveMQConsumerKernel::deliverAcks()
> (ActiveMQConsumerKernel.cpp:1257)
> ==7369==    by 0xF9BAB04:
> activemq::core::kernels::ActiveMQConsumerKernel::dispose()
> (ActiveMQConsumerKernel.cpp:845)
> ==7369==    by 0xF9EFC53:
> activemq::core::kernels::ActiveMQSessionKernel::dispose()
> (ActiveMQSessionKernel.cpp:379)
> ==7369==    by 0xF9F09A8:
> activemq::core::kernels::ActiveMQSessionKernel::doClose()
> (ActiveMQSessionKernel.cpp:306)
> ==7369==    by 0xF9F103F:
> activemq::core::kernels::ActiveMQSessionKernel::close()
> (ActiveMQSessionKernel.cpp:296)
> ==7369==    by 0xF962466: activemq::core::ActiveMQSession::close()
> (ActiveMQSession.cpp:62)
>
> ActiveMQConn::terminateConnection(GCONcontext*) (ActiveMQConn.cc:1148)
>
> It is observed while calling terminateConnection from my client code as
> above.
>
> Can anyone please help in this regard?
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/activemq-cpp-library-3-8-2-memory-leak-tp4684233.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>
Try the latest release v3.8.3 to see if the issue has already been 
resolved.  If not then a test that can be added to the current set that 
will show the error under valgrind will help us to track it down.

-- 
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.bish@redhat.com | www.fusesource.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/


Mime
View raw message