[
https://issues.apache.org/jira/browse/TAP5-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533251#comment-13533251
]
Hudson commented on TAP5-1977:
------------------------------
Integrated in tapestry-trunk-freestyle #977 (See
[https://builds.apache.org/job/tapestry-trunk-freestyle/977/])
TAP5-1977: Memory leak (perm gen) in component reloading (Revision
f0a72c48904eee28e95f3ddd1f7847004aefd766)
Note fixed bug TAP5-1977 (Revision ea240ddf29814a234edfde900d867872b08630c9)
Result = FAILURE
hlship :
Files :
* tapestry-core/src/main/java/org/apache/tapestry5/services/TapestryModule.java
hlship :
Files :
* 54_RELEASE_NOTES.txt
> 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, 5.4
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
