[
https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37702
]
Nathan Mittler commented on AMQCPP-27:
--
I've added a couple of tweaks to trunk. If this doesn't work I think Valgrind
is giving us a phantom memory leak.
[
https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37703
]
Albert Strasheim commented on AMQCPP-27:
Valgrind still reports this leak on Linux, but Purify says all clear on
Windows. I'll take a closer sometime in
[
https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37706
]
Nathan Mittler commented on AMQCPP-27:
--
Ok, I think I got it. Grab the latest activemq/concurrent/Thread.cpp and give
that a try.
> Issues reported by Val
[
https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37753
]
Nathan Mittler commented on AMQCPP-27:
--
I haven't heard back - was this resolved by my latest changes?
> Issues reported by Valgrind when running unit test
[
https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37765
]
Albert Strasheim commented on AMQCPP-27:
Haven't gotten round to this yet -- but I'll be putting our code that uses
AMQCPP through a thorough Valgrind/Pu
[
https://issues.apache.org/activemq/browse/AMQCPP-27?page=comments#action_37772
]
Albert Strasheim commented on AMQCPP-27:
Still get the same "leak" with the latest trunk. I'm beginning to think that is
is probably leak in my glibc or