myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Korherr (JIRA)" <>
Subject [jira] Commented: (MYFACES-2942) Memory Leak in MyFaces 2.0.1 probably as well in 2.0.2
Date Sat, 16 Oct 2010 19:34:24 GMT


Jakob Korherr commented on MYFACES-2942:

I tested a lot of scenarios locally to find out why the WebappClassLoader is not GCed, but
I did not find a result.

I locally removed all ThreadLocal instances from the MyFaces code and also fixed the problem
with the WeakHashMap mentioned by Stan, but the WebappClassLoader still isn't GCed.

Suggestions are welcome...

> Memory Leak in MyFaces 2.0.1 probably as well in 2.0.2
> ------------------------------------------------------
>                 Key: MYFACES-2942
>                 URL:
>             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.

View raw message