[richfaces-issues] [JBoss JIRA] Updated: (RF-4471) Usage of ImageIO in ResourceBuilderImpl causes memory leak

Nick Belaevski (JIRA) jira-events at lists.jboss.org
Tue Jul 13 11:39:04 EDT 2010


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

Nick Belaevski updated RF-4471:
-------------------------------

    Fix Version/s: 4.0.0.Milestone2
                       (was: 4.0.0.Milestone1)


> Usage of ImageIO in ResourceBuilderImpl causes memory leak
> ----------------------------------------------------------
>
>                 Key: RF-4471
>                 URL: https://jira.jboss.org/browse/RF-4471
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: core
>    Affects Versions: 3.1.6
>         Environment: any
>            Reporter: Philipp Schoepf
>            Assignee: Nick Belaevski
>             Fix For: 4.0.0.Milestone2
>
>
> It seems as we found a memleak in the ResourceBuilderImpl class. The call to 
> ImageIO.setCache(false)
> causes sun.awt.AppContext to statically initialize itself (inside static initialization of IIORegistry). The problem is that AppContext seems to hold a static reference to the contextclassloader of the calling thread. When our application gets undeployed the reference to the applications classloader is still hold by AppContext causing that loaded classes cannot be garbage collected.
> I only checked richfaces 3.16 but if ResourceBuilderImpl still exists in 3.2 stream I suppose that the problem exists there as well.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the richfaces-issues mailing list