Community
Participate
Working Groups
Created attachment 242110 [details] Projects that reproduce the bug I recently installed the Java 8 support for Eclipse Kepler and started to use some Java 8 features. I am also using the nullity checking annotations. Now one or more files in my project seems to be causing a StackOverflowError when it is built, opened, or saved. Creating a workspace and importing the projects from the attachment was enough to reproduce the issue as a build error for me. Also, trying to open the file /banjo-lang/src/banjo/dom/core/CoreExprTreeFold.java causes the decoration calculation version of the error. If you think of a temporary workaround please let me know! eclipse.buildId=4.3.2.M20140221-1700 java.version=1.8.0_05 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.standard.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.standard.product This is a continuation of log file E:\projects\banjo\eclipse-workspace\.metadata\.bak_0.log Created Time: 2014-04-16 22:20:19.202 Error Thu Apr 17 22:30:30 PDT 2014 An internal error occurred during: "Decoration Calculation". java.lang.StackOverflowError at org.eclipse.jdt.internal.compiler.lookup.TypeVariableBinding.nullAnnotatedReadableName(TypeVariableBinding.java:728) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1116) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1085) at org.eclipse.jdt.internal.compiler.lookup.TypeVariableBinding.nullAnnotatedReadableName(TypeVariableBinding.java:728) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1116) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1085) ... repeats for a long time ... eclipse.buildId=4.3.2.M20140221-1700 java.version=1.8.0_05 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.standard.product Command-line arguments: -data E:\projects\banjo\temp-workspace -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.standard.product Error Thu Apr 17 22:50:51 PDT 2014 An internal error occurred during: "Building workspace". java.lang.StackOverflowError at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1089) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1085) at org.eclipse.jdt.internal.compiler.lookup.TypeVariableBinding.nullAnnotatedReadableName(TypeVariableBinding.java:728) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1116) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1085) at org.eclipse.jdt.internal.compiler.lookup.TypeVariableBinding.nullAnnotatedReadableName(TypeVariableBinding.java:728) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1116) at org.eclipse.jdt.internal.compiler.lookup.ParameterizedTypeBinding.nullAnnotatedReadableName(ParameterizedTypeBinding.java:1085) at org.eclipse.jdt.internal.compiler.lookup.TypeVariableBinding.nullAnnotatedReadableName(TypeVariableBinding.java:728) ... and so on ...
Getting a smaller test case is difficult. The workspace becomes unusable after the exception is hit. Will try to extract one.
Shankha, can you reproduce this in HEAD? I'd suspect this to be a duplicate of the (already fixed) bug 431269
Hi Stephan, You may be write. I cannot reproduce the exact NPE reported in Comment 0. I see a different NPE on HEAD. ReferenceBinding.isCompatibleWith The reason could be: otherType being NULL. Call stack: -------------------------------------------------------------------- java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.lookup.ReferenceBinding.isCompatibleWith(ReferenceBinding.java:1237) at org.eclipse.jdt.internal.compiler.lookup.TypeBinding.isCompatibleWith(TypeBinding.java:590) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.areReturnTypesCompatible(MethodVerifier.java:91) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.areReturnTypesCompatible(MethodVerifier.java:80) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.checkAgainstInheritedMethods(MethodVerifier.java:163) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier15.checkAgainstInheritedMethods(MethodVerifier15.java:386) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier15.checkMethods(MethodVerifier15.java:586) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.verify(MethodVerifier.java:970) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier15.verify(MethodVerifier15.java:999) at org.eclipse.jdt.internal.compiler.lookup.MethodVerifier.verify(MethodVerifier.java:979) at org.eclipse.jdt.internal.compiler.lookup.SourceTypeBinding.verifyMethods(SourceTypeBinding.java:2507) at org.eclipse.jdt.internal.compiler.lookup.CompilationUnitScope.verifyMethods(CompilationUnitScope.java:796) at org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:767) at org.eclipse.jdt.internal.compiler.ProcessTaskManager.run(ProcessTaskManager.java:137) at java.lang.Thread.run(Thread.java:744) --------------------------------------------------------------- I will update more about the cause. Thanks
(In reply to shankha banerjee from comment #3) > Hi Stephan, > You may be write. Sorry. I meant you may be correct.
I think it is a duplicate of https://bugs.eclipse.org/bugs/show_bug.cgi?id=431269, actually, I missed that other issue in my searches. Sorry about that. *** This bug has been marked as a duplicate of bug 431269 ***
Shankha, the NPE you reported in comment 3: is it reproduceable? Is it triggered by the same sources? If you can reproduce but little/no connection to bug 431269 please file a new bug, thanks.
By the way I updated to a recent integration build and now I am getting the NullPointerException that Shanka mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=433063#c3 . Was another ticket filed for that?
(In reply to Dobes Vandermeer from comment #7) > By the way I updated to a recent integration build and now I am getting the > NullPointerException that Shanka mentioned in > https://bugs.eclipse.org/bugs/show_bug.cgi?id=433063#c3 . Was another > ticket filed for that? Sorry. I had not filed the report. Bug 433478. Thanks
