[richfaces-issues] [JBoss JIRA] (RF-13025) MemoryLeak: SerializedViewCollection filled with org.richfaces.renderkit.ResourceLibraryRenderer

[Michael Heinen (JIRA)]

     [ https://issues.jboss.org/browse/RF-13025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Heinen updated RF-13025:
--------------------------------

    Steps to Reproduce: 
- Start the sample application
- call <sampleApp>/faces/index.xhtml
- click two times "RichFaces Post" button
-> take a heapDump
- click few more times times "RichFaces Post" button
-> take another heapDump
Compare the size of the SerializedViewCollection objects

  was:
- Start the sample application
- call <sample>pp>/faces/index.xhtml
- click two times "RichFaces Post" button
-> take a heapDump
- click few more times times "RichFaces Post" button
-> take another heapDump
Compare the size of the SerializedViewCollection objects


    
> MemoryLeak: SerializedViewCollection filled with org.richfaces.renderkit.ResourceLibraryRenderer
> ------------------------------------------------------------------------------------------------
>
>                 Key: RF-13025
>                 URL: https://issues.jboss.org/browse/RF-13025
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core
>    Affects Versions: 4.2.2.Final, 4.3.2
>         Environment: Richfaces 4.2.2 (happens also with Richfaces 4.3.2)
> myfaces 2.1.10 (happens also with 2.1.11)
> Tomcat 6.0.36
>            Reporter: Michael Heinen
>         Attachments: Dump20Clicks.jpg, Dump2Clicks.jpg, zSessionLeak.war
>
>
> The SerializedViewCollection grows in my application with every ajax call.
> A new reference to a "org.richfaces.renderkit.ResourceLibraryRenderer" is added each time.
> This happens only if the page contains a <a4j:ajax> tag.
> Without any <a4j:ajax> tag the SerializedViewCollection doesn't grow!
> A sample application will be attached as well as screenshots with the heap dumps.
> The Heapdumps are also available.

--
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