Community
Participate
Working Groups
in EMF (most likely related to Gerrit as I know of nothing else I use using EMF). see next comment for trace
Created attachment 233637 [details] stack trace turns out this is too long for a comment
Thomas, what did you do?! :)
Wow, great summary :) I guess I was in a rush and didn't check. Anyway, I had some issues with gerrit...I think in regards to task 413362, and at some point saw this stacktrace here. Whether they are related or not I can't say. I also didn't notice a specific action triggering it. All I did was closing/reopening gerrit editors, synchronizing tasks, expanding/collapsing the broken patchset section...
Created attachment 233672 [details] another stackoverflow another stackoverflow, this time when pressing "Publish Comments". Patchset issue still exists. I will revert to a previous version now, Gerrut unusable currently
Tomek, do you have any idea what might be causing this? I have never seen it.
Thomas, are you able to reproduce this?
I saw it twice. I reverted to a released as I don't have the time to deal with my workspace breaking continuously :(
(In reply to comment #5) > Tomek, do you have any idea what might be causing this? No, sorry. I've never seen anything like this in my workspace, but the stack looks similar to bug 408729. At least the repeating part of it: at org.eclipse.emf.ecore.util.EcoreEList.resolve(EcoreEList.java:161) at org.eclipse.emf.ecore.util.EObjectContainmentWithInverseEList$Resolving.resolve(EObjectContainmentWithInverseEList.java:105) at org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:348) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eObjectForURIFragmentSegment(BasicEObjectImpl.java:539) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.getEObject(ResourceImpl.java:774) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.getEObject(ResourceImpl.java:750) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(ResourceSetImpl.java:223) at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:197) at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:257) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eResolveProxy(BasicEObjectImpl.java:1473)
Thanks for finding that.
This is *definitely* some kind of issue with persistence. See bug 413362 -- something must have become corrupted, and I'll need to take a look at the data to try to figure out what.
I checked with Thomas and he is using a directory with spaces for workspace, e.g. "C:\work\workspaces\to work from". This implicates bug 413480 but I'm not ready to mark as dup until we verify that.
*** Bug 413362 has been marked as a duplicate of this bug. ***
(In reply to comment #11) > I checked with Thomas and he is using a directory with spaces for workspace, > e.g. "C:\work\workspaces\to work from". This implicates bug 413480 but I'm not > ready to mark as dup until we verify that. I associated this with wrong bug. I believe that this is actually the same root cause as dup bug below. Thomas, please reopen if you see this after applying change. (You may need to delete the existing workspace metadata as well, see Bug 413362 comment 10. *** This bug has been marked as a duplicate of bug 413957 ***
Miles, While it appears the stack overflow is not happening, I am now observing bug 414460, bug 414461 and bug 414464 (the latter sounds a lot like it's related to this one and bug 413362).
(sorry, accidentally reopened) *** This bug has been marked as a duplicate of bug 413957 ***
