Community
Participate
Working Groups
F1 ViewPanes still stack around after you close them scenario: close the navigator the ViewPane instance that had the navigator is still there (sometimes it is reused, sometimes not (like in the case of PackageExpolorer) - i could not figure that out) they should be removed and if they cannot be, then they should at least free their memory od dispose() (i.e. nullify the fields)
Do you have the Navigator open in another perspective in the same window?
sorry, don't remember now but i don't think so
Kevin, one leak test we should do on today's build is: - close all perspectives - open Resource perspective - check number of instances of ResourceNavigator (should be 1) - close ResourceNavigator - check number of instances of ResourceNavigator (should be 0) - reopen ResourceNavigator - check number of instances of ResourceNavigator (should be 1)
Added println(s) to Resourcenavigator and we are calling dispose when the view is closed in all perspectives.
Tested it using Optimizeit. The Navigator had a reference to it in some cases. Fix PartTabFolder. Released in the HEAD stream.
Reopening. Backing out the fix in PartTabFolder. It has side efects. See bug 18929.
The leak is less critical than the layout problems. This area is too risky to change at this point for 2.0.
Can we resolve it as LATER?
Sure.
What is leaking?
The View itself. The method dispose gets called but we keep one reference to the view which may be eventualy released.
Reopened for investigation
Fix is already released in the 2.1 stream.
