[jboss-jira] [JBoss JIRA] Commented: (JBAOP-461) Resolve outstanding issues on Linux

[ http://jira.jboss.com/jira/browse/JBAOP-461?page=comments#action_12414729 ] Flavia Rainone commented on JBAOP-461: -------------------------------------- Removing the ThreadLocal instances of JoinPointGenerator.AroundAdviceCallStrategy class solved the memory leak on JProfiler. However, this is not the solution for this issue. I have configured JProfiler to run with precompiled classes. The tests with JBoss Profiler use javaagent (I haven't managed to do so with JProfiler). The fact that now we don't have any more memory leaks with JProfiler (i.e., precompiled classes), but still see the memory leaks with JBoss Profiler, is a strong indicator that the memory leak cause lies in the javaagent mechanism. This would explain why we only see the memory leaks in linux. The javaagent mechanism is a low level one, and is probably impelemented via native code. So, its Linux implementation differs from the Windows one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira