[
https://issues.apache.org/jira/browse/TOMEE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476035#comment-13476035
]
Romain Manni-Bucau commented on TOMEE-465:
------------------------------------------
Hi,
Well, hard to work on it, i managed to reproduce the issue but was not linked
directly to the singleton itself which was not totally allocated when the JVM
crashed (but previous instance was cleaned up).
not sure how to get more information on it, looking the dump it seems String
are mainly taking the memory, can maybe be linked to a "too fast" reloading of
the app
moreover observing the memory on a case where no "big static attribute" is
present the memory is correctly freeed.
> Classloader memory leak on redeployment
> ---------------------------------------
>
> Key: TOMEE-465
> URL: https://issues.apache.org/jira/browse/TOMEE-465
> Project: TomEE
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Harald Wellmann
> Attachments: tomee-leak.zip
>
>
> Redeploying the attached webapp a couple of times in a row (e.g. by modifying
> and saving the source file in Eclipse with WTP and automatic publishing
> enabled) leads to an OutOfMemoryError.
> Inspecting the heap with Eclipse Memory Analyzer, I see stale copies of the
> LeakingSingleton class having the contextClassLoader of an
> org.apache.openejb.scheduler.pool thread as GC root.
> Tested with apache-tomee-1.5.1-20121014.041023-38-webprofile.zip
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
