Bug 250412 - StackOverflowError when saving Java file
Summary: StackOverflowError when saving Java file
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: 3.6 M4   Edit
Assignee: Olivier Thomann CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2008-10-10 06:32 EDT by Ilja Preuss CLA
Modified: 2009-12-10 09:05 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ilja Preuss CLA 2008-10-10 06:32:11 EDT
Build ID: M20080911-1700

Steps To Reproduce:
I have a Java class with a constructor calling another constructor via this(parameters...). The called constructor now has an additional argument. When I add that same argument to the end of the parameter list of this constructor and hit ctrl-s, the following Exception occurs (reproducibly, for the current state of the workbench).

More information:
java.lang.StackOverflowError
	at org.eclipse.jdt.internal.compiler.lookup.Binding.isValidBinding(Binding.java:91)
	at org.eclipse.jdt.core.dom.DefaultBindingResolver.getMethodBinding(DefaultBindingResolver.java:230)
	at org.eclipse.jdt.core.dom.MethodBinding.getMethodDeclaration(MethodBinding.java:423)
	at org.eclipse.jdt.core.dom.DefaultBindingResolver.findDeclaringNode(DefaultBindingResolver.java:170)
	at org.eclipse.jdt.core.dom.CompilationUnit.findDeclaringNode(CompilationUnit.java:327)
	at org.eclipse.jdt.internal.corext.dom.ASTNodes.findDeclaration(ASTNodes.java:235)
	at org.eclipse.jdt.internal.corext.fix.VariableDeclarationFix$VariableDeclarationFinder.callsWrittingConstructor(VariableDeclarationFix.java:291)
	at org.eclipse.jdt.internal.corext.fix.VariableDeclarationFix$VariableDeclarationFinder.callsWrittingConstructor(VariableDeclarationFix.java:295)
... (that last line 1017 more times)
Comment 1 Philipe Mulet CLA 2008-10-10 07:30:08 EDT
Ilja - could pls you provide the testcase as an attachment ?
Comment 2 Ilja Preuss CLA 2008-10-10 10:45:05 EDT
No, sorry, couldn't reproduce in a reasonably sized testcase. The class this happened with depended on the existence of a 1.5GB workspace. After I changed a *different* class, it also didn't happen again. It might be that I also used features like quick assist or similar in a slightly different way.

Sorry, I fear I can't be of much more help. As the problem somehow went away now, I reduced the severity of this bug entry.
Comment 3 Jerome Lanneluc CLA 2008-10-14 04:48:14 EDT
There is not much we can do without more information.
Comment 4 Olivier Thomann CLA 2009-12-09 10:23:38 EST
Closing as WORKSFORME.
No info provided.
Reopen if you can provide the requested information.
Comment 5 Ilja Preuss CLA 2009-12-09 10:55:26 EST
The problem never happened again to me.
Comment 6 Satyam Kandula CLA 2009-12-10 01:17:11 EST
Verified for 3.6M4 using Build id: I20091209-0100
Comment 7 Olivier Thomann CLA 2009-12-10 09:05:38 EST
Verified.