Bug 65769 - Ctrl-shift-T stops working
Summary: Ctrl-shift-T stops working
Status: RESOLVED DUPLICATE of bug 57419
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 RC3   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-04 14:07 EDT by Stefan Xenos CLA
Modified: 2004-06-07 13:32 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 Stefan Xenos CLA 2004-06-04 14:07:34 EDT
After using Eclipse for awhile, Ctrl-shift-T stopped working. It would open a
progress dialog indicating that it was doing some work, but the progress meter
stopped partway. Opening up the task manager revealed that Eclipse was not using
any CPU time. 

The progress dialog could be cancelled and it was possible to continue using
Eclipse without the "go to type" feature.

I found this in my log (not sure if it's the same thing):

!ENTRY org.eclipse.jdt.core 4 4 Jun 04, 2004 12:05:33.03
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.IllegalArgumentException: Buffer size <= 0
	at java.io.BufferedInputStream.<init>(BufferedInputStream.java(Inlined Compiled
Code))
	at java.io.BufferedInputStream.<init>(BufferedInputStream.java(Inlined Compiled
Code))
	at
org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable(DiskIndex.java(Compiled
Code))
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategory(DiskIndex.java:360)
	at
org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategories(DiskIndex.java:352)
	at
org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(DiskIndex.java(Compiled
Code))
	at org.eclipse.jdt.internal.core.index.Index.save(Index.java:171)
	at
org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(IndexManager.java:491)
	at
org.eclipse.jdt.internal.core.search.indexing.SaveIndex.execute(SaveIndex.java:40)
	at
org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:367)
	at java.lang.Thread.run(Thread.java:568)
Comment 1 Kent Johnson CLA 2004-06-06 08:26:13 EDT
Which VM are you running?

Suspect this is a duplicate of bug 57419.
Comment 2 Kent Johnson CLA 2004-06-07 13:32:20 EDT
Released a small works around so we avoiding calling the simple constructor.

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