Bug 13234 - Can't open type
Summary: Can't open type
Status: RESOLVED DUPLICATE of bug 9296
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: Other Linux-Motif
: P3 normal (vote)
Target Milestone: 2.0 M6   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-10 08:46 EDT by Jared Burns CLA
Modified: 2002-04-25 05:05 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jared Burns CLA 2002-04-10 08:46:09 EDT
Build 20020409
Linux-motif
I just created a brand new workspace. I brought in the projects I'm a committer
for (debug core, debug ui, jdt debug core, jdt debug ui, jdt launching, j9
launching) from the dev.eclipse.org repository. Then I imported the required
projects for jdt ui as binaries from the 20020409 build.

When I click the "Open type" button, a progress dialog comes up that says
"Searching...   31 files to index"

However, nothing happens. The dialog's progress monitor stays at the start
position and my CPU is idle.
Comment 1 Jared Burns CLA 2002-04-10 08:48:01 EDT
It should be noted that there were no errors in my log and the problem went away
when I restarted Eclipse. However, during that first launch I hit the "Open
type" button repeatedly and got the same problem.
Comment 2 Erich Gamma CLA 2002-04-10 19:08:29 EDT
could be related to http://bugs.eclipse.org/bugs/show_bug.cgi?id=13395

moving to Core for investigation
Comment 3 Philipe Mulet CLA 2002-04-11 04:15:44 EDT
Indeed this could be the same issue. Question though: had you switched to the 
Java perspective prior to loading/importing projects into it ?
Comment 4 Jared Burns CLA 2002-04-11 08:31:39 EDT
Yes (99.9% certain). The first thing I do when I create a new workspace is go to
the Java perspective.
Comment 5 Philipe Mulet CLA 2002-04-11 09:52:23 EDT
Then it might not be the same problem, which was due to some CP variable being 
initialized inside the indexer thread.

If it occurs to you again, please provide an execution stack dump (ctrl-pause 
in console) so that we can investigate further.
Comment 6 Jerome Lanneluc CLA 2002-04-11 11:12:56 EDT
I could not reproduce on a clean build 20020409.
Comment 7 Philipe Mulet CLA 2002-04-17 14:08:32 EDT
I start thinking that the indexer thread died in the background maybe due to a 
jit bug ? Were you running the IBM jdk with jit on ?
Comment 8 Jared Burns CLA 2002-04-17 14:18:08 EDT
I never pass the -jit option into the VM when I launch Eclipse. I run with the
default JIT setting, whatever that is.
Comment 9 Jared Burns CLA 2002-04-17 14:18:51 EDT
It should be noted that I haven't seen this problem since I reported it.
Comment 10 Philipe Mulet CLA 2002-04-19 04:42:26 EDT
By default the JIT is on, you can disable it with "-Djava.compiler=none".
This JIT has known defects, and a better one should soon be available.
Comment 11 Philipe Mulet CLA 2002-04-25 05:05:37 EDT
Could be a combination of a JIT problem or a duplicate of bug 9296

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