Memory leak in WorkbenchPage.activationList
Steps to reproduce
We found a memory leak in WorkbenchPage when using e4 Parts. In the activationList all MPart are added due to E4PartListener.partActivated(). But the removal from that list is done only for CompatibilityPart in firePartClosed().
See https://github.com/eclipse-platform/eclipse.platform.ui/blob/cb121fe0f1b0bb270d8cfbc266092df0fd1de743/bundles/org.eclipse.ui.workbench/Eclipse%20UI/org/eclipse/ui/internal/WorkbenchPage.java#L5080
So after opening and closing a lot of editors more and more objects are kept in memory in this list.
Community
- [x] I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.
Do you want to contribute a fix? If not, please provide some steps how to reproduce or a minimal test.
Currently I want not to contribute a fix.
Even a simple example that reproduces the problem would help...
i took a headump on an eclipse instance that was used for 6 hours and i could not find significant amount leaked:
closing as not planned
i could not find significant amount leaked:
Because Eclipse is not using (native) e4 parts. Last time I checked the compatibility layer was used. There (only) the removal is handled correctly.