[ https://issues.apache.org/jira/browse/PIVOT-861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422238#comment-13422238 ]
Sandro Martini edited comment on PIVOT-861 at 7/25/12 3:29 PM: --------------------------------------------------------------- Hi David, I just committed the test case under branches/2.0.x/tests/ ... a little reworked, but mainly to add some more info and log, and to adapt to the new package: org.apache.pivot.tests.issues.pivot861 The main (Test Application) class is (as usual) Pivot<Bug number>.java In next days I'll start to work in the fix :-) ... and only later merge in trunk (now targeted for 2.1.0). If you have suggestions/comments tell us. Thank you very much. was (Author: smartini): Hi David, thank you very much, I'll try asap and say something. > Memory leak: Window icon ImageListenerList retains reference to closed > windows, preventing garbage collection > ------------------------------------------------------------------------------------------------------------- > > Key: PIVOT-861 > URL: https://issues.apache.org/jira/browse/PIVOT-861 > Project: Pivot > Issue Type: Bug > Components: wtk, wtk-media > Affects Versions: 2.0.2 > Environment: Windows XP, Java 1.7.0_05 > Reporter: David Keen > Assignee: Sandro Martini > Priority: Minor > Fix For: 2.0.3 > > Attachments: leaktest.zip > > > When a window or dialog is opened which has an icon, after it is closed it > cannot be garbage collected because a reference is retained to it through the > icon. Removing the icon resolves the issue. > As far as I've investigated, the issue appears to the in the > ImageListenerList which each Image contains. I've done a heapdump of my > application and used the IBM HeapAnalyzer which shows this list containing a > reference to the window/dialog through the ImageViewSkin, but I don't know > the Pivot internals well enough to see where or how it should be released. > I'll attach a simple test application to show the issue. -- 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