Community
Participate
Working Groups
I have a workspace with about 100 Java projects in it. I can no longer start Eclipse because java.exe crashes on startup. There is no javacore dump - the only trace is in the .log file shown below, which shows a recursive loop in subTypeOfType(). !ENTRY org.eclipse.ui 4 0 Nov 29, 2002 11:42:12.611 !MESSAGE java.lang.StackOverflowError !STACK 0 java.lang.StackOverflowError at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.superclass (BinaryTypeBinding.java(Compiled Code)) at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.subTypeOfType (HierarchyResolver.java(Compiled Code)) [... repeated hundreds of times...] org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.subTypeOfType (HierarchyResolver.java(Compiled Code)) at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.subOrSuperOfFocus (HierarchyResolver.java:536) at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.reportHierarchy (HierarchyResolver.java:349) at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.resolve (HierarchyResolver.java(Compiled Code)) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.buildForProje ct(IndexBasedHierarchyBuilder.java:229) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.buildFromPote ntialSubtypes(IndexBasedHierarchyBuilder.java:331) at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.build (IndexBasedHierarchyBuilder.java:164) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.compute (TypeHierarchy.java:270) at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refresh (TypeHierarchy.java:1140) at org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.executeOperation (CreateTypeHierarchyOperation.java:69) at org.eclipse.jdt.internal.core.JavaModelOperation.execute (JavaModelOperation.java:305) at org.eclipse.jdt.internal.core.JavaModelOperation.run (JavaModelOperation.java:513) at org.eclipse.jdt.internal.core.JavaModelManager.runOperation (JavaModelManager.java:1204) at org.eclipse.jdt.internal.core.JavaElement.runOperation (JavaElement.java:574) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy (BinaryType.java:475) at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy (BinaryType.java:464) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefr esh(TypeHierarchyLifeCycle.java:148) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.access$0 (TypeHierarchyLifeCycle.java:133) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle$1.run (TypeHierarchyLifeCycle.java:109) at org.eclipse.jdt.internal.ui.util.BusyIndicatorRunnableContext$BusyRunnable.inter nalRun(BusyIndicatorRunnableContext.java:107) at org.eclipse.jdt.internal.ui.util.BusyIndicatorRunnableContext$BusyRunnable.run (BusyIndicatorRunnableContext.java:74) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:66) at org.eclipse.jdt.internal.ui.util.BusyIndicatorRunnableContext.run (BusyIndicatorRunnableContext.java:120) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.ensureRefreshed TypeHierarchy(TypeHierarchyLifeCycle.java:117) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyViewPart.updateInput (TypeHierarchyViewPart.java:407) at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyViewPart.setInputElement (TypeHierarchyViewPart.java:393) at org.eclipse.jdt.internal.ui.util.OpenTypeHierarchyUtil.openInViewPart (OpenTypeHierarchyUtil.java:120) at org.eclipse.jdt.internal.ui.util.OpenTypeHierarchyUtil.open (OpenTypeHierarchyUtil.java:97) at org.eclipse.jdt.ui.actions.OpenTypeHierarchyAction.run (OpenTypeHierarchyAction.java:119) at org.eclipse.jdt.ui.actions.OpenTypeHierarchyAction.run (OpenTypeHierarchyAction.java:111) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun (SelectionDispatchAction.java:197) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run (SelectionDispatchAction.java:175) at org.eclipse.jface.action.Action.runWithEvent(Action.java:749) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection (ActionContributionItem.java:407) at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent (ActionContributionItem.java(Compiled Code)) at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent (ActionContributionItem.java(Compiled Code)) at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent (ActionContributionItem.java(Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java (Compiled Code)) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java (Compiled Code)) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1239) at org.eclipse.core.internal.boot.InternalBootLoader.run (InternalBootLoader.java:775) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:462) at java.lang.reflect.Method.invoke(Native Method) at org.eclipse.core.launcher.Main.basicRun(Main.java:247) at org.eclipse.core.launcher.Main.run(Main.java:703) at org.eclipse.core.launcher.Main.main(Main.java:539)
Tim, which build are you using?
AFAIK, I was using the final release of 2.0.1: Version: 2.0.1 Build id: 200208291828 FYI, I tried the 2.1 M3 build instead, and I was able to start the same workspace. I'm not sure if this was fixed by another defect, or the upgrade just happened to get around the problem. Since I am able to start Eclipse again, this is not as urgent an issue for me. However, other 2.0.1 users may also hit the problem and may be less open to upgrading to a new version.
Thanks. I was asking this because I remember we changed something in this area recently (I can't find the bug number right now). If customers of the 2.0.1 release need the fix, it would mean we need to backport it to the 2.0 maintenance stream. AFAIA this stream is closed (2.0.2 is out). So I will close this bug since it works for you now. Please don't hesitate to reopen if you see the problem in a 2.1 build.
Old, closing.
