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

[Alexander Schwartz (JIRA)]

    [ https://jira.jboss.org/jira/browse/RF-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12457323#action_12457323 ] 

Alexander Schwartz commented on RF-4471:
----------------------------------------

See this

http://forums.java.net/jive/thread.jspa?messageID=121561

for a workaround, that works for me (at least on tomcat)

Alexander.

> Usage of ImageIO in ResourceBuilderImpl causes memory leak
> ----------------------------------------------------------
>
>                 Key: RF-4471
>                 URL: https://jira.jboss.org/jira/browse/RF-4471
>             Project: RichFaces
>          Issue Type: Bug
>    Affects Versions: 3.1.6
>         Environment: any
>            Reporter: Philipp Schoepf
>            Assignee: Tsikhon Kuprevich
>             Fix For: 3.3.1
>
>
> 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/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira