tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-1977) Memory leak (perm gen) in component reloading
Date Fri, 20 Jul 2012 18:39:34 GMT

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

Howard M. Lewis Ship closed TAP5-1977.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.3.5
         Assignee: Howard M. Lewis Ship

Fixed in the 5.4-js-rewrite branch as well; will update here when that is merged.
                
> 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
>             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

        

Mime
View raw message