Bugzilla – Full Text Bug Listing
| Summary: | Workspace Becomes Corrupted | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Ken Taylor <archon358> |
| Component: | IDE | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bsd, daniel_megert, loskutov |
| Version: | 4.5.2 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 8 | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=459833 | ||
| Whiteboard: | stalebug | ||
|
Description
Ken Taylor
Can you really correlate the broken workspace with the ConcurrentModificationException exception in ServiceLocator? If yes, we can close this bug as a dup of bug 459833. If not, please try to use 4.6 and see if this will fix your problem. He seems to be using 4.6, Andrey:
> -- Configuration Details --
> Product: Eclipse 4.6.0.20160613-1800 (org.eclipse.epp.package.jee.product)
> Installed Features:
> org.eclipse.platform 4.6.0.v20160606-1342
(In reply to Brian de Alwis from comment #2) > He seems to be using 4.6, Andrey: > > > -- Configuration Details -- > > Product: Eclipse 4.6.0.20160613-1800 (org.eclipse.epp.package.jee.product) > > Installed Features: > > org.eclipse.platform 4.6.0.v20160606-1342 I can't understand how then the stack of 4.6 contains this line: ServiceLocator.dispose(ServiceLocator.java:136) For 4.5 it would be OK. I don't get it either. Ken: in 4.6, line 136 of ServiceLocator doesn't call next(). Indeed, the code was changed for 4.6 to avoid a ConcurrentModificationException like your report, such that there are no calls to next() in 4.6's ServiceLocator. Your stack trace does align with 4.5.2. The error was in 4.5 and 4.4. I simply created the issue in 4.6, so you can ignore that aspect. I'm pretty sure the exception is what caused the corrupted workspace but the only way to tell is to find out what exactly got corrupted and manually fix it and then try to open that workspace in Eclispe. Update: I accidently launched the broken version, then realized my mistake and killed the Eclipse process. Then Eclipse actually came up. I tried this several times. Seems like something wrong with the Eclipse launcher. Is that some kind of service wrapper? I updated that version and did a restart, problem remained. I then did a complete shutdown and restart of Eclipse. Now problem is gone. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |