[ https://issues.apache.org/activemq/browse/AMQCPP-26?page=all ]

Albert Strasheim resolved AMQCPP-26.
------------------------------------

    Fix Version/s: 1.1
       Resolution: Fixed

> Memory leaks reported by Rational Purify when running unit tests
> ----------------------------------------------------------------
>
>                 Key: AMQCPP-26
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-26
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
>             Fix For: 1.1
>
>         Attachments: vc2005-activemq-unittests-purify.txt
>
>
> Rational Purify reports two potential memory leaks in the latest ActiveMQ C++ 
> code from SVN. I've attached the complete Purfiy output.
> Look for the following:
> MPK: Potential memory leak of 116 bytes from 1 block allocated in 
> activemq::core::ActiveMQConnectionFactory::createConnection(basic_string<char,char_traits<char>::std,allocator<char>::std>::std
>  const&,basic_string<char,char_traits<char>::std,allocator<char>::std>::std 
> const&,basic_string<char,char_traits<char>::std,allocator<char>::std>::std 
> const&) [vc2005-activemq-unittests.exe]
> Potential memory leak of 116 bytes from 1 block allocated in 
> activemq::core::ActiveMQConnectionFactory::createConnection(basic_string<char,char_traits<char>::std,allocator<char>::std>::std
>  const&,basic_string<char,char_traits<char>::std,allocator<char>::std>::std 
> const&,basic_string<char,char_traits<char>::std,allocator<char>::std>::std 
> const&) [vc2005-activemq-unittests.exe]
> I think the createConnection leak has also been reported on the mailing list.
> Complete Purify output attached.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to