[
https://issues.apache.org/jira/browse/MYFACES-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12922338#action_12922338
]
Jakob Korherr commented on MYFACES-2942:
----------------------------------------
@Martin: I am using the sample app from the myfaces archetypes (really, really
small) and tomcat 7.0.2, 6.0.29 and 6.0.20.
I just committed a solution which removes all ThreadLocals, which we can't
really guarantee to be removed(), from the code and uses
FacesContext.getAttributes() instead, because this is also local for the
current Thread, but will certainly be released.
Furthermore I put the MetadataTarget cache from MetaRulesetImpl on the
Application Map, thus these instances will certainly be removed upon undeploy,
regardless of the WebappClassLoader beeing GCed. Furthermore this also gets rid
of the problems with multiple webapps in a shared classloader scenario
(Application Maps are unique per webapp).
However, tomcat (all versions) still tells me that there is a possible memory
leak in my mini-app. But again, if I use the profiler I can't find any non-weak
non-soft references to the WebappClassLoader, but it really is still there. One
good thing though is that the WebappClassLoader is now a lot smaller (not even
1 MB), because all MetadataTarget instances are gone.
Further suggestions are appreciated! I think we are really near to an
acceptable solution.
> Memory Leak in MyFaces 2.0.1 probably as well in 2.0.2
> ------------------------------------------------------
>
> Key: MYFACES-2942
> URL: https://issues.apache.org/jira/browse/MYFACES-2942
> Project: MyFaces Core
> Issue Type: Bug
> Affects Versions: 2.0.1, 2.0.2
> Environment: JBOSS AS
> Reporter: Werner Punz
> Assignee: Jakob Korherr
> Priority: Critical
> Attachments: MYFACES-2942-RuntimeConfig.patch
>
>
> Stan Silvert from JBoss reports:
> I'm pretty sure 2.0.1 has a memory leak on undeploy. Mojarra had an undeploy
> leak and it took a long time to track it down. The same test I was using on
> Mojarra also failed on MyFaces but I haven't had time to track down the leak
> in MyFaces.
> Maybe this is fixed in 2.0.2? If not maybe someone can go ahead and take a
> look? The mem leak keeps MyFaces from passing TCK on JBoss AS. To test, all
> you need to do is create a small exploaded JSF app. Then have a script that
> touches web.xml every 10 seconds. That will cause the app to redeploy. You
> will get a PermGen error in about an hour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
