Community
Participate
Working Groups
M20120909-2000. Objects are leaked in a simple close/open text editor scenario. Simple test case: 0. start new workspace 1. prepare a perspective with only the Navigator view open with a text file in it 2. reset the instance counter of your profiler 3. open the editor 4. close the editor ==> several instances are leaked, e.g. XMLMemento, EclipseContext, NavigationHistoryEntry, ValueComputation, etc.
(In reply to comment #0) > ==> several instances are leaked, e.g. XMLMemento, EclipseContext, > NavigationHistoryEntry, ValueComputation, etc. At least NavigationHistoryEntry is probably not a leak because it is OK to be kept in the navigation history.
(In reply to comment #1) > At least NavigationHistoryEntry is probably not a leak because it is OK to > be kept in the navigation history. Correct, the XMLMemento, NavigationHistoryEntry, TextSelectionNavigationLocation, and related XML elements are not leaks. The are used by the navigation history which by a set depth of 50 (NavigationHistory#CAPACITY). Once you reach the capacity it releases the older entries. (Can be verified by changing capacity to, say, 3. Those elements no longer appear in memory snapshot deltas after 3 open/close cycles.)
*** Bug 391138 has been marked as a duplicate of this bug. ***
(In reply to comment #3) > *** Bug 391138 has been marked as a duplicate of this bug. *** This bug contains a possible patch for a leak.
You mean attachment 221913 [details] ? Eric recently changed the handling of the intermediate composite when he moved the grab handles into CSS. PW
(In reply to comment #5) > You mean attachment 221913 [details] [diff] ? > > Eric recently changed the handling of the intermediate composite when he > moved the grab handles into CSS. > > PW Look at the history of bug 391138 and you know it ;-).
I released the ToolBarManagerRenderer patch - thanks Snjezana! http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R4_2_maintenance&id=e9b68830bd95c74a0821e544efca4d943ec6b79e
The common part closing/opening issues have being resolved in bug 389250 . Several specific editor issues were resolved under this bug, in the bug 391138, and in the bug 391253.
Verified using I20121030-0800 and M20121024-1600.
(In reply to comment #8) > The common part closing/opening issues have being resolved in bug 389250 . > Several specific editor issues were resolved under this bug, in the bug > 391138, and in the bug 391253. Verified this in N20130114-2000: much better now!