activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Closed: (AMQCPP-322) Found memory leaks in ActiveMQCPP
Date Wed, 27 Oct 2010 13:03:00 GMT


Timothy Bish closed AMQCPP-322.

    Resolution: Cannot Reproduce

Working through some of the locations that are shown here I've not been able to find any that
actually leak, the memory is released as expected.  I think the leak tracker being used is
confused by the smart pointers and loses track of the memory allocation / deallocation points.
 Older versions of valgrind had similar issues.

> Found memory leaks in ActiveMQCPP
> ---------------------------------
>                 Key: AMQCPP-322
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 3.2.3
>         Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util
1.3.9, apr iconv 1.2.1
>            Reporter: Helen Huang
>            Assignee: Timothy Bish
>             Fix For: 3.2.4
>         Attachments:, Memory Leaks.xml, MemoryLeaks1.JPG,
MemoryLeaks2.JPG, MemoryLeaks3.JPG
> We found a large number of memory leaks in ActiveMQCPP and APR while we ran DevPartner
error detection. We are wondering if  you can fix them in branch 3.2.4? Thank you very much
for your help in advance!
> We saved a copy of the error detection report. Attached please find the file.  Also we
did restart the message broker during our test. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message