[jbosstools-issues] [JBoss JIRA] (JBIDE-11539) Memory leak in org.jboss.tools.jst.web.kb
Viacheslav Kabanovich (JIRA)
jira-events at lists.jboss.org
Fri Apr 20 12:25:18 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12686139#comment-12686139 ]
Viacheslav Kabanovich commented on JBIDE-11539:
-----------------------------------------------
Sigi, please first just let me know how many entries
key: org.eclipse.core.internal.resources.File
value: org.jboss.tools.jst.web.kb.internal.XmlContextImpl
are in the map, and how many xml files are in your workspace.
Theoretically, kb model can keep one entry for each xml file. It is a cache to be used for next builds and searches.
I have looked into the lifecycle of this map's content, and could not find a case of memory leak: as soon as a resource is renamed or removed, all out-of-date entries are removed. So let us please first check the case of your workspace being too big for the set VM memory arguments.
> Memory leak in org.jboss.tools.jst.web.kb
> -----------------------------------------
>
> Key: JBIDE-11539
> URL: https://issues.jboss.org/browse/JBIDE-11539
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 3.3.0.Beta2
> Environment: Windows XP
> Eclipse 3.7
> JBoss Tools(over marketplace, last update 4/11/2012
> Reporter: Sigi Kiermayer
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 3.3.0.Beta3
>
>
> I have huge memory problems and two days ago i made a heap dump and got following information:
> The classloader/component "org.jboss.tools.jst.web.kb" occupies 485,306,072 (76.24%) bytes. The memory is accumulated in one instance of "java.util.HashMap$Entry[]" loaded by "<system class loader>".
> Keywords
> java.util.HashMap$Entry[]
> org.jboss.tools.jst.web.kb
> It is full of HashMapentries:
> key: org.eclipse.core.internal.resources.File
> value: org.jboss.tools.jst.web.kb.internal.XmlContextImpl
> I have the memory dump here. i can provide it if you think it is a reproducible bug or you have an idea how that can happen.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list