Bug 82773

Summary: New Class Wizard Superclass field *painfully* slow
Product: [Eclipse Project] JDT Reporter: Marco Qualizza <mlq.eclipse>
Component: CoreAssignee: JDT-Core-Inbox <jdt-core-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: martinae
Version: 3.1   
Target Milestone: 3.1 RC2   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Marco Qualizza CLA 2005-01-13 13:58:34 EST
Create a new class using the New Class wizard, and, in the wizard, enter the
name of the super class.  There is a *painful* pause for every keypress.  The
problem is that findType is being called 3 times for every key press.  The
second call (NewTypeWizardPage 1300) against java.lang is expensive, and the
third call (NTWP 1305) is *super* expensive (against my project, which has ~6000
types).  I'm sorry, but I can't go any deeper since I really don't know the
Eclipse source code. :-)
Comment 1 Dirk Baeumer CLA 2005-01-23 12:22:18 EST
Martin, can you please comment.
Comment 2 Martin Aeschlimann CLA 2005-01-24 05:35:17 EST
I realize that 'findType' is not the cheapest method, but so far we never had a
complaint, nor have I experienced what you describe. I have over 14000 types in
my project. I also thought that jdt.core has a type cache for the project.
Is this always like that? Can you check the log for other problems?

Moving to jdt.core to comments.
We do 3 'find types' to find the (unqualified) name in the current package, the
java.lang package, or as fully qualified name.

Comment 3 Marco Qualizza CLA 2005-01-24 12:38:36 EST
It was happening on Friday, but now it does happen.  I tried restarting Eclipse
(it had been on all weekend) but that didn't help.  I cannot see anything in the
log file.
Comment 4 Marco Qualizza CLA 2005-01-24 12:39:07 EST
Sorry, it was *not* happening on Friday.
Comment 5 Olivier Thomann CLA 2005-06-07 09:56:00 EDT
Can you reproduce with latest?
If not, we will close as WORKSFORME.
Comment 6 Philipe Mulet CLA 2005-06-11 16:00:26 EDT
Closing as not reproduced recently. 
Please reopen if you still see a problem and have steps to reproduce.