Project: Eclipse_Platform_UI
Bug 284604 [Compatibility] Working the e4 SDK gets slower and slower
Reported: 2009-07-24 13:36:36 | Status: resolved fixed

Over time as we open and close editors, we "leak" runAndTrack(*). We create a number of runAndTrack Runnables for various things, including one for each editor that iterates through the tab items. These runnables lifecycle are tied to the renderer, but the lifecycle of the IEclipseContext is tied to the model (which exists for as long as its MContributedPart). There are 2 parts to this in the short term: 1) If the runAndTrack is tied to SWT resources (like the CTabItem/ETabItem) it should go away when the part is disposed. 2) the model add that creates the context (currently org.eclipse.e4.workbench.ui.internal.Workbench.initializeContext(IEclipseContext, MPart<?>) ) should also makes sure it disposes the context on remove. PW

Files changed in fix:
bundles/org.eclipse.e4.ui.workbench.renderers.swt/src/org/eclipse/e4/workbench/ui/renderers/swt/StackRenderer.java bundles/org.eclipse.e4.ui.workbench/src/org/eclipse/e4/workbench/ui/internal/Trackable.java