This content has been marked as final.
Show 4 replies
-
1. Re: 3.0.0.CR1 Memory Leak
hchiorean Oct 9, 2012 2:34 AM (in response to bwallis42)Hi Brian,
Not sure what the ImmortalCacheValue is (which does sound scary ), but I have a suspicion that "parentReferenceToSelfParent" which was introduced as a fix for MODE-1613 might be causing this.
-
2. Re: 3.0.0.CR1 Memory Leak
hchiorean Oct 9, 2012 4:24 AM (in response to hchiorean)I've opened https://issues.jboss.org/browse/MODE-1670, as I hope it's the cause for the issue you are seeing.
-
3. Re: 3.0.0.CR1 Memory Leak
bwallis42 Oct 9, 2012 6:20 AM (in response to hchiorean)I tried a second secnario that didn't store anything large enough to go into the binary store but it still seemed to leak. I'm running now under the profiler but it is very slowwwww...... Will update with the results if I get any.
-
4. Re: 3.0.0.CR1 Memory Leak
hchiorean Oct 9, 2012 6:28 AM (in response to bwallis42)If my "theory" from MODE-1670 is correct, the leak wouldn't be related to binary storage, but to the fact that cache entries (even though they may be evicted from the cache) are never claimed by the GC.