| Summary: | EMFBasedPersister - Memory Leak | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Christian Dietrich <christian.dietrich.opensource> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sebastian.zarnekow |
| Version: | unspecified | Flags: | sebastian.zarnekow:
indigo+
|
| Target Milestone: | SR2 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
Pushed to master. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |
Build Identifier: 2.0.0 2.0.1 Xtext uses EMFBasedPersister to keep the Index during a restart of eclipse. This leads to following problem: (1) We have a workspace with 2+ projects (2) on start EMFBasedPersister loads the index using an xmiresource. the reference to the xmireasourse with all its contents is kept through ResourceDescriptionsData (3) starting a clean build on one projects leads to a replacement of the corresponding resourcedescriptions in ResourceDescriptionsData.addDescription(URI, IResourceDescription) (4) but the old ones stay still alive cause there is still a reference from the other resourcesecriptions to the xmiresource (5) => if the project is clean is very very big and the other very small then this will lead to a nearly doubling of consumed memory Reproducible: Always