You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Jakob Korherr (JIRA)" <de...@myfaces.apache.org> on 2010/12/11 16:01:01 UTC

[jira] Reopened: (MYFACES-2942) Memory Leak in MyFaces 2.0.1 probably as well in 2.0.2

     [ https://issues.apache.org/jira/browse/MYFACES-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jakob Korherr reopened MYFACES-2942:
------------------------------------


Reopened, because it must be fixed for MyFaces core 1.2.x too.

> 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
>             Fix For: 2.0.3-SNAPSHOT
>
>         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.