[BTRACE-76] Memory Leak of ThreadEnteredMap using TLS about btrace HOT 3 CLOSED

[author="pilfrich", created="Mon, 8 Aug 2011 14:38:50 +0200"]

Investigation update
I've just re-checked the behavior without @tls - simply by invoking a probe action for each thread. In this scenario the threads are stored in the ThreadEnteredMap too. For every probe fired the current thread is added to the ThreadEnteredMap and kept there until the application exits.

from btrace.

[author="j.bachorik", created="Mon, 8 Aug 2011 15:10:38 +0200"]

Indeed, all the application threads are kept as hard references. Changing this to weak references should prevent this kind of leak.

http://kenai.com/projects/btrace/sources/hg/revision/425

from btrace.

[author="pilfrich", created="Wed, 10 Aug 2011 01:38:12 +0200"]

Re-checked with revision 425. I still got a lot more garbage collection than without BTrace, but in an expected manner.
Tested with 120k threads over 4 hours with ~2m probes firing over each 15secs interval and the use of ThreadLocals. Memory leak fix confirmed.

Thanks again for the quick fix

from btrace.