Bug 346606 - [navigation] Quick Type Hierarchy and 'Open Implementation' blocks UI
Summary: [navigation] Quick Type Hierarchy and 'Open Implementation' blocks UI
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug fix candidate
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-20 04:35 EDT by Dani Megert CLA
Modified: 2024-01-03 12:18 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2011-05-20 04:35:25 EDT
3.2.

We do show progress in the status line at the beginning when the TH is computed but then we start to open the information control we spend cycles in the UI before the control gets opened.

Ctrl+T at least shows the busy cursor during that time but 'Open Implementation' hyperlink shows the arrow cursor.


Test Case:
	void test(C c) {
		Object o;
		if (o.equals(this))
			System.out.println();
	}



Stack Trace:
"main" prio=6 tid=0x002b7000 nid=0x15c0 runnable [0x0090d000]
   java.lang.Thread.State: RUNNABLE
        at java.io.WinNTFileSystem.getLastModifiedTime(Native Method)
        at java.io.File.lastModified(File.java:826)
        at java.util.zip.ZipFile.<init>(ZipFile.java:127)
        at java.util.zip.ZipFile.<init>(ZipFile.java:144)
        at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2673)
        at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar(JarPackageFragmentRoot.java:153)
        at org.eclipse.jdt.internal.core.ClassFile.getJarBinaryTypeInfo(ClassFile.java:343)
        at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:279)
        at org.eclipse.jdt.internal.core.ClassFile.getBinaryTypeInfo(ClassFile.java:273)
        at org.eclipse.jdt.internal.core.ClassFile.buildStructure(ClassFile.java:83)
        at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:258)
        at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:518)
        at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:255)
        at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:241)
        at org.eclipse.jdt.internal.core.BinaryType.getClassFileInfo(BinaryType.java:229)
        at org.eclipse.jdt.internal.core.BinaryType.getChildren(BinaryType.java:192)
        at org.eclipse.jdt.internal.core.JavaElement.getChildrenOfType(JavaElement.java:210)
        at org.eclipse.jdt.internal.core.BinaryType.getMethods(BinaryType.java:460)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.hasCompatibleMethod(TypeHierarchyContentProvider.java:120)
        - locked <0x179b4580> (a org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider$1)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.hasMemberFilterChildren(TypeHierarchyContentProvider.java:323)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.isInTree(TypeHierarchyContentProvider.java:309)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.hasTypeChildren(TypeHierarchyContentProvider.java:337)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.isInTree(TypeHierarchyContentProvider.java:309)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.hasTypeChildren(TypeHierarchyContentProvider.java:337)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.isInTree(TypeHierarchyContentProvider.java:309)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.addTypeChildren(TypeHierarchyContentProvider.java:300)
        at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyContentProvider.getChildren(TypeHierarchyContentProvider.java:256)
        at org.eclipse.jdt.internal.ui.typehierarchy.HierarchyInformationControl.setInput(HierarchyInformationControl.java:295)
        at org.eclipse.jface.text.AbstractInformationControlManager.internalShowInformationControl(AbstractInformationControlManager.java:1181)
        at org.eclipse.jface.text.AbstractInformationControlManager.presentInformation(AbstractInformationControlManager.java:1150)
        at org.eclipse.jface.text.AbstractInformationControlManager.setInformation(AbstractInformationControlManager.java:418)
        at org.eclipse.jface.text.information.InformationPresenter.computeInformation(InformationPresenter.java:355)
        at org.eclipse.jface.text.AbstractInformationControlManager.doShowInformation(AbstractInformationControlManager.java:1131)
        at org.eclipse.jface.text.AbstractInformationControlManager.showInformation(AbstractInformationControlManager.java:1121)
        at org.eclipse.jdt.internal.ui.javaeditor.JavaSourceViewer.doOperation(JavaSourceViewer.java:187)
        at org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor$AdaptedSourceViewer.doOperation(CompilationUnitEditor.java:200)
        at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:128)
Comment 1 Eclipse Genie CLA 2022-01-11 12:14:11 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2024-01-03 12:18:27 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.