Bug 69036 - Java search got blocked by indexing (for a long time)
Summary: Java search got blocked by indexing (for a long time)
Status: CLOSED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo, performance
Depends on:
Blocks:
 
Reported: 2004-06-30 12:26 EDT by Dirk Baeumer CLA
Modified: 2009-08-30 02:04 EDT (History)
1 user (show)

See Also:


Attachments
The VM dump (125.68 KB, application/octet-stream)
2004-06-30 12:26 EDT, Dirk Baeumer CLA
no flags Details
JVM Dump 2 (108.92 KB, application/octet-stream)
2004-07-02 11:44 EDT, Jean-Philippe Gariepy CLA
no flags Details
JVM Dump (10.42 KB, text/plain)
2004-11-10 13:12 EST, Jean-Philippe Gariepy CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Baeumer CLA 2004-06-30 12:26:06 EDT
3.0

I tried to open a type via Open Type, but I always got a searching progress 
dialog which didn't make any progress. 

Producing a stack dump showed that the searching for all types was waiting on 
the indexer to finish. Hoewever I waited for ca 2 minutes and produced several 
VM dumps and they all showed the same stack traces.
Comment 1 Dirk Baeumer CLA 2004-06-30 12:26:54 EDT
Created attachment 12913 [details]
The VM dump
Comment 2 Philipe Mulet CLA 2004-06-30 12:47:38 EDT
Any steps to reproduce ?
Comment 3 Dirk Baeumer CLA 2004-06-30 13:32:29 EDT
No, after killing Eclipse and restarting the search worked.
Comment 4 Jean-Philippe Gariepy CLA 2004-07-02 11:42:31 EDT
I'm running eclipse 3.0RC2 under Linux and I've got the same symptoms.

>java -version
java version "1.4.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1)
Classic VM (build 1.4.1, J2RE 1.4.1 IBM build cxia321411-20040301 (JIT enabled:
jitc))

I've also had this problem many times using eclipse 3.0 (M8, M9 and RC2) under
Sun JVM 1.4.2.

We may speculate that this is some sort of deadlock in java indexing.

This does not occur systematically but when I have the problem once, it will
always occur for the remaining of the session.  I always have to exit Eclipse to
make the java indexer work correctly.   I can trigger the problem with "Open
Type..." in the Navigate menu and every other places in Eclipse where I can pick
a java type  from a list (i.e. when creating a class, choosing the supertype by
clicking on Browse...).

I've attached another dump.
Comment 5 Jean-Philippe Gariepy CLA 2004-07-02 11:44:01 EDT
Created attachment 12943 [details]
JVM Dump 2
Comment 6 Kent Johnson CLA 2004-09-02 13:07:15 EDT
Please reopen if you can reproduce on 3.0.1.

BTW: the IBM build cxia321411-20040301 is not trustworthy. There are newer 
versions of this VM available.
Comment 7 Jean-Philippe Gariepy CLA 2004-11-10 13:12:55 EST
Created attachment 15782 [details]
JVM Dump

I've got the problem using Sun VM.

%java -version

java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
Comment 8 Jean-Philippe Gariepy CLA 2004-11-10 13:15:50 EST
Forgot to mention this occurs in 

Version: 3.0.1
Build id: 200409161125
Comment 9 Philipe Mulet CLA 2005-04-07 09:15:22 EDT
reopening
Comment 10 Philipe Mulet CLA 2005-04-07 09:16:13 EDT
Does it still occur on latest ? If so, then please reopen with steps.
Comment 11 Frederic Fusier CLA 2005-05-24 08:00:29 EDT
I think we can close this one as no feedback has been done on 3.0 for more than
six months.

This issue should not concern 3.1 because Open Type dialog as completely changed.
Comment 12 Denis Roy CLA 2009-08-30 02:04:51 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.