Bugzilla – Full Text Bug Listing
| Summary: | OutOfMemoryError (Java Heap Space) when resolving bundles | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Thomas Watson <tjwatson> |
| Component: | Framework | Assignee: | Thomas Watson <tjwatson> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | blocker | ||
| Priority: | P3 | CC: | hargrave, jean.barata, Martin.Halle, matthieu.helleboid, tjwatson |
| Version: | 3.10.0 Luna | ||
| Target Milestone: | Luna SR2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 457118 | ||
| Bug Blocks: | |||
|
Description
Thomas Watson
Only considering backporting the following commit that fixes the immediate issue in the Felix resolver: http://git.eclipse.org/c/equinox/rt.equinox.framework.git/commit/?id=e7db81bab4bce237fcafd3d624e56d183bbd6dae The other changes in bug 457118 are performance enhancements in the Equinox code that calls the felix resolver. These may not be appropriate for backporting. I got a gerrit review for this on the R4_4_maintenance branch: https://git.eclipse.org/r/#/c/39783/ BJ, could you review? (In reply to Thomas Watson from comment #2) > I got a gerrit review for this on the R4_4_maintenance branch: > > https://git.eclipse.org/r/#/c/39783/ > > BJ, could you review? Reviewed. I released the fix as well as the test from master. I am badly struggling with this bug on Luna SR2. I read the comments carefully and it seems there will be no easy Luna fix/update. What can I do to have my project working again? A downgrade to Kepler is not possible for me. Any instructions of how to bypass this would be REALLY helpful! (In reply to Martin Halle from comment #5) > I am badly struggling with this bug on Luna SR2. > > I read the comments carefully and it seems there will be no easy Luna > fix/update. > > What can I do to have my project working again? A downgrade to Kepler is not > possible for me. Any instructions of how to bypass this would be REALLY > helpful! We will need some steps to reproduce. The initial issue this defect was raised for was fixed in SR2. It seems you have run into a separate issue. It would be helpful if you could open a separate defect so we can track it separately. > We will need some steps to reproduce. The initial issue this defect was
> raised for was fixed in SR2. It seems you have run into a separate issue.
> It would be helpful if you could open a separate defect so we can track it
> separately.
I think its resolved now, SR2 really fixed it. I tried a completely fresh Luna SR2 installation and this time I was able to start the project.
For the record:
1.) I did update Luna to SR2. Although I cleaned the installation by deleting the history I had both (org.eclipse.osgi_3.10.1.xxx and org.eclipse.osgi_3.10.2.xxx) packages installed - the one of SR1 and SR2. So there was the chance to pick the wrong one.
2.) For the my application under development to run I used a referenced (non-default) config.ini file. After I enabled the option to clear it (Run configurations -> tab "Configuration" -> "Clear the configuration file before launching") the application ran without trouble. Most likely the config.ini file referenced the SR1 packages (I didn't keep a copy, unfortunately).
I hope this helps others with the same problem - thank you, this thread helped me a lot to understand the problem.
|