Summary: | New Class Wizard Superclass field *painfully* slow | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Marco Qualizza <mlq.eclipse> |
Component: | Core | Assignee: | 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
2005-01-13 13:58:34 EST
Martin, can you please comment. 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. 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. Sorry, it was *not* happening on Friday. Can you reproduce with latest? If not, we will close as WORKSFORME. Closing as not reproduced recently. Please reopen if you still see a problem and have steps to reproduce. |