Bug 81438 - [index] Adding invalid jar on the classpath causes long delays in hierarchy
Summary: [index] Adding invalid jar on the classpath causes long delays in hierarchy
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.2 M5   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-16 12:51 EST by Jerome Lanneluc CLA
Modified: 2006-02-03 11:22 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jerome Lanneluc CLA 2004-12-16 12:51:58 EST 
I20041216

1. Workspace with all JDT Core projects as source
2. Add a 'Test' Java project.
3. Create empty file '/Test/mylib.jar' (it has 0 bytes so it is an invalid jar)
4. Add mylib.jar to the classpath of Test
5. Open hierarchy on ASTNode
Observe: This takes an excessively long time to be computed
Comment 1 Jerome Lanneluc CLA 2004-12-16 12:53:13 EST 
Looks like we permanently try to reindex the invalid jar.
Also we add launch many ProgressJobs in JobManager.run().
Comment 2 Philipe Mulet CLA 2006-02-03 04:36:27 EST 
Is this still an issue ?
Comment 3 Frederic Fusier CLA 2006-02-03 11:22:22 EST 
No, it's not => close as WORKSFORME