[ https://issues.apache.org/activemq/browse/AMQCPP-28?page=comments#action_37704 ] Albert Strasheim commented on AMQCPP-28: ----------------------------------------
Purify and Valgrind both still report this leak: ==14253== 206 (40 direct, 166 indirect) bytes in 2 blocks are definitely lost in loss record 3 of 3 ==14253== at 0x4005BA5: operator new(unsigned) (vg_replace_malloc.c:163) ==14253== by 0x805447F: Producer::run() (ExpirationTest.cpp:124) ==14253== by 0x80635DC: activemq::concurrent::Thread::runCallback(void*) (Thread.cpp:165) ==14253== by 0xAC83DA: start_thread (in /lib/libpthread-2.5.so) ==14253== by 0xA2206D: clone (in /lib/libc-2.5.so) Purify also still reports a few issues, but less than in the first log I submitted. I'll attach the new log now. > Purify and Valgrind warnings when running integration tests > ----------------------------------------------------------- > > Key: AMQCPP-28 > URL: https://issues.apache.org/activemq/browse/AMQCPP-28 > Project: ActiveMQ C++ Client > Issue Type: Bug > Affects Versions: 1.1 > Reporter: Albert Strasheim > Assigned To: Nathan Mittler > Attachments: activemq-cpp-test-integration-valgrind.log, > vc2005-activemq-integration-tests-purify.txt > > > Warnings from Purify when running the integration test (latest from trunk) > against latest trunk of the broker. -- 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
