Bug 96162 - Open Type dialog blocking on indexing
Summary: Open Type dialog blocking on indexing
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-05-20 16:03 EDT by Jonathan Feinberg CLA
Modified: 2009-08-30 02:08 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 Jonathan Feinberg CLA 2005-05-20 16:03:02 EDT
The Open Type dialog comes up with a few types in it; there is a message beneath
the text entry box saying "Refreshig indices...(6%)". The number does not
change, and no new types populate the box.
Comment 1 Dirk Baeumer CLA 2005-05-21 06:20:43 EDT
The new dialog uses search indices which in your scenario aren't accurate right
now. When this happened, did Eclipse crash before or did you heavily rearrange
your workspace. Then indecing might take a while however you should see
progress. Can you preproduce the scenario where no progress on "Refreshing
indices" was reported?

When the dialog is refreshing the search indices it already shows the entries
from the history to give you access to the last opened types. So in general is
is the expected bahviour. What is not expected is that you don't see any
progress on the index refreshing.

Comment 2 Jonathan Feinberg CLA 2005-05-21 12:58:30 EDT
When the described event happened, Eclipse 31M7 had been running for a couple of
days, with normal behavior.

From the moment the described event took place, until I restarted Eclipse--a
period of about 24 hours--there was no further progress in indexing whenever I
attempted to use the Open Type dialog.

After quitting eclipse, the javaw process continued, and I had to nuke it via
the task manager (resulting in the Eclipse jvm termination dialog). Since
restarting, it has behaved correctly.

If I can find reproducible steps, I'll post them right away. In the meantime,
I'd consider WORKSFORME to be legitimate, as long as I could reopen it later.
Comment 3 Dirk Baeumer CLA 2005-05-23 07:13:59 EDT
Jonathan,

a reproducable case would be a big help here or if it happens again the stack
trace of the VM that doesn't close/shotdown. From qhat you are decribing it
looks like the index background thread is hanging. As a result indices aren't
updated anymore and Eclipse doesn't shutdown.

Setting PR to remind.
Comment 4 Denis Roy CLA 2009-08-30 02:08:38 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.