Community
Participate
Working Groups
Created attachment 253935 [details] Stack trace Hi, This the third workspaces I'm breaking with that problem. I have a workspace with some java projects that I do not want to build (I unchecked the "Project>Build Automatically" button). I'm working on a project that writtes some files in all those projects using "Joob" mechanism. Sometimes (I have failed to find a procedure to reproduce this all the time) when I start my runtime platform I get a dialog saying that: _____________________________________________________________ "An internal error occured during: "Decoration Calculation" _____________________________________________________________ "Decorating Calculation" "Initializing Java Tooling" _____________________________________________________________ "An internal error occurred during: "Decoration Calculation". java.lang.StackOverflowError" _____________________________________________________________ I have attached the stacktrace to this bug. Regards, Arthur
This problem occurs when JDT tries to resolve project dependencies. I don't think it's about the code you wrote, but about the way your projects depend on each other. E.g. circular project dependencies (although that should actually be supported or report an error if that setting is enabled on the Java > Compiler > Building preference page). Here's the repeating part of the stack trace: at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2848) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1932) at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:3247) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2693) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2857) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1962) at org.eclipse.jdt.internal.core.ProjectReferenceChange.updateProjectReferencesIfNecessary(ProjectReferenceChange.java:47) at org.eclipse.jdt.internal.core.ChangeClasspathOperation.classpathChanged(ChangeClasspathOperation.java:59) at org.eclipse.jdt.internal.core.SetContainerOperation.executeOperation(SetContainerOperation.java:110) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:729) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:794) at org.eclipse.jdt.internal.core.JavaModelManager$9.run(JavaModelManager.java:2832) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
JDT Core team: AFAICS, JavaModelManager#CONTAINER_INITIALIZATION_IN_PROGRESS et al. should take care of cycles. Maybe the problem is that access to JavaModelManager#previousSessionContainers and/or other fields is not synchronized? I didn't see anything obvious, and I'll stop my investigations for now.
Hi Markus, First of all thanks for looking into this problem. Some extra information: The projects imported in my workspace are old legacy code that is known to have cycle dependencies. However, I was surprised that Eclipse tries to build it even if I have removed the "Build Automatically" preference. Regarding the preference you mentioned, in my workspace the preference is set to report an error. However, it does not report anything. Instead it crashes on a StackOverFlowError. regards, Arthur
(In reply to Arthur Daussy from comment #3) > However, I was surprised that Eclipse tries to > build it even if I have removed the "Build Automatically" preference. (In reply to Arthur Daussy from comment #0) > when I start my runtime platform This always builds required projects if "Preferences > Run/Debug > Launching > Build (if required) before launching" is enabled.
My apologies if I was not clear enought. The projects with cycle dependencies are in my "runtime" workspace. It is not in the workspace that I use to create my runtime platform. The error is displayed after launching my runtime platform when it tries to initialize the Java Tooling in my "runtime" workspace.
*** Bug 473552 has been marked as a duplicate of this bug. ***
Sorry ran out of time in M1.
Sorry, have to move it out.
*** Bug 480647 has been marked as a duplicate of this bug. ***
Sorry, moving out. No progress yet.
Not much hope for M7. Tentatively keeping on 4.6 list.
Sorry, no hope for 4.6. Bulk moving to 4.7.
Bulk move out of 4.8
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.
