You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2012/08/07 00:55:03 UTC

[jira] [Updated] (TAP5-1977) Memory leak (perm gen) in component reloading

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

Howard M. Lewis Ship updated TAP5-1977:
---------------------------------------

    Labels: fixed-in-5.4-js-rewrite  (was: )
    
> Memory leak (perm gen) in component reloading
> ---------------------------------------------
>
>                 Key: TAP5-1977
>                 URL: https://issues.apache.org/jira/browse/TAP5-1977
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.4, 5.3
>            Reporter: Denis Delangle
>            Assignee: Howard M. Lewis Ship
>              Labels: fixed-in-5.4-js-rewrite
>             Fix For: 5.3.5
>
>         Attachments: memoryleak.patch
>
>
> I think I found a memory leak in components reloading. The ComponentEventResultProcessor uses a StrategyBuilder to find the correct behavior to apply on events methods results.
> If a "onEvent" method returns a component instance, then the StrategyBuilder will keep the component class in its cache. When reloading components, this cache should be cleared to let GC clear the classLoader and all the corresponding classes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira