[ https://issues.jboss.org/browse/JBIDE-20750?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-20750 at 9/22/15 11:38 PM: ------------------------------------------------------------------------- I have found one reference to KbProject object that is not released, so the memory leak exists and technically can be resolved by removing this reference only. When testing results, I compared this solution with the other where also method dispose() was implemented on KbObject. It turns out that if objects are released for garbage collection in few large structures (like the entire KbProject), JVM may 'tolerate' them as long as it approaches memory limit. On the other hand, if large structures are dissected into 'atoms', JVM may invoke garbage collector even if these objects take in total just a couple of Mb. was (Author: scabanovich): I have found one reference to KbProject object that is not released, so the memory leak exists and technically can be resolved by removing this reference only. When testing results, I compared this solution with the other where also method dispose() was implemented on KbObject. It turns out that if objects are released for garbage collection in few large structures (like the entire KbObject), JVM may 'tolerate' them as long as it approaches memory limit. On the other hand, if large structures are dissected into 'atoms', JVM may invoke garbage collector even if these objects take in total just a couple of Mb. -- This message was sent by Atlassian JIRA (v6.4.11#64026)