eclipse-platform / eclipse-platform/eclipse.platform

ever growing DeltaDataTree history (performance, leaked memory)

Open
#359 0 comments 0 reactions 0 assignees View on GitHub
bug performance
Dominant language
Java
Stars
165
Forks
174
Avg merge
2d 8h
Merged PRs (30d)
22

Description

We observe, that eclipse is getting slower and slower while using it. After restarting it's faster.
We now have an example where the heapdump shows 39_483 org.eclipse.core.internal.dtree.DeltaDataTree/org.eclipse.core.internal.watson.ElementTree for only 956 org.eclipse.core.internal.resources.Project.
see https://github.com/eclipse-pde/eclipse.pde/issues/510#issuecomment-1472080130
i.e. a Tree with depth of 39483 / a history of such many changes in workspace.
My understanding is that the depth should be at most equal to the number of Projects build, because after Autobuild of each project the current state of the project should advance to the current workspace state and old states should be cleaned up.

The heapdump shows also that many ElementTree are hold by the builders in org.eclipse.core.internal.events.InternalBuilder.oldState

My first guess what happens is that only a subset of projects are changed. Then autobuild skips unchanged projects. Then the skipped projects keep their ancient state. Then all intermediate workspace states may stay in memory.

I currently don't have the time for further investigation :-(

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.