Bug 41711

Summary: code analysis endlessly loops and report errors even before saving
Product: [Eclipse Project] JDT Reporter: quartz quartz <quartz12h>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3    
Version: 3.0   
Target Milestone: 3.0 M3   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description quartz quartz CLA 2003-08-19 14:50:23 EDT
I edit a program. Once I type the open brace, without closing it, it pops the
error view. It keeps switching focus from editor to error view, so I can't
change barely change the source to prevent it. It does that many times, over and
over. I didn't save yet, no ctrl-s. Just typing my own business... and pow!
Grrrr...


java.lang.NullPointerException
	at
org.eclipse.jdt.internal.compiler.ast.ExplicitConstructorCall.analyseCode(ExplicitConstructorCall.java:69)
	at
org.eclipse.jdt.internal.compiler.ast.ConstructorDeclaration.analyseCode(ConstructorDeclaration.java:92)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.internalAnalyseCode(TypeDeclaration.java:615)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.analyseCode(TypeDeclaration.java:211)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.internalAnalyseCode(TypeDeclaration.java:597)
	at
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.analyseCode(TypeDeclaration.java:251)
	at
org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.analyseCode(CompilationUnitDeclaration.java:77)
	at org.eclipse.jdt.internal.compiler.Compiler.resolve(Compiler.java:595)
	at
org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:172)
	at
org.eclipse.jdt.internal.core.CompilationUnit.buildStructure(CompilationUnit.java:139)
	at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:198)
	at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:448)
	at
org.eclipse.jdt.internal.core.CompilationUnit.makeConsistent(CompilationUnit.java:881)
	at
org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:48)
	at
org.eclipse.jdt.internal.core.JavaModelOperation.execute(JavaModelOperation.java:365)
	at
org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:704)
	at org.eclipse.jdt.internal.core.JavaElement.runOperation(JavaElement.java:484)
	at
org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:994)
	at
org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:970)
	at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:72)
	at
org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:99)
	at org.eclipse.jface.text.reconciler.MonoReconciler.process(MonoReconciler.java:76)
	at
org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:189)
Comment 1 Olivier Thomann CLA 2003-08-19 15:38:34 EDT
This looks like a duplicate of bug 40995.
It will be in tomorrow's integration build. You can also patch the 
org.eclipse.jdt.core plugin with the patch available on the JDT/Core web page. 
Let me know if this is fixing this issue and I will close it as a duplicate.
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-
home/r3.0/main.html#updates
Comment 2 Olivier Thomann CLA 2003-08-20 08:36:59 EDT

*** This bug has been marked as a duplicate of 40995 ***