[jbosstools-issues] [JBoss JIRA] (JBIDE-20750) Slow Memory Leak in JSF tools

[Viacheslav Kabanovich (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-20750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13111535#comment-13111535 ] 

Viacheslav Kabanovich commented on JBIDE-20750:
-----------------------------------------------

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.

> Slow Memory Leak in JSF tools
> -----------------------------
>
>                 Key: JBIDE-20750
>                 URL: https://issues.jboss.org/browse/JBIDE-20750
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: jsf
>    Affects Versions: 4.3.0.CR1
>            Reporter: Denis Golovin
>            Assignee: Viacheslav Kabanovich
>            Priority: Critical
>             Fix For: 4.3.1.Final, 4.4.0.Alpha1
>
>         Attachments: .log, heap-snapshot1.png, heap-snapshot2.png, mem-usage.png, oom1.png, oom2.png
>
>
> Opening then closing jsf projects slowly consumes heap memory, whish leads to slowing down overal performance and eventually to GC overhead limit exceeded exceptions.
> Attached screenshot list:
> 1. GC overhead limit exceeded error [^oom1.png];
> 2. Heap Memory Usage timeline [^mem-usage.png];
> 3. Heap Memory Objects filtered for "org.jboss.tools" [^heap-snapshot2.png];
> 4. Heap Memory Objects none filtered [^heap-snapshot1.png];
> 5. OOM Dialog [^oom2.png]ж
> 6. [^.log]



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)