Bug 91440 - AbstractMethodError from jface
Summary: AbstractMethodError from jface
Status: RESOLVED DUPLICATE of bug 65098
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-14 14:51 EDT by Tom Musta CLA
Modified: 2005-04-28 04:44 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 Tom Musta CLA 2005-04-14 14:51:29 EDT
At seemingly random times, I will get flooded with error popup windows (push OK,
get another one, push OK, get another, etc.).  The stack trace from my log is
below.  I am on R3.1M6.

My apologies if this is a duplicate .... I searched the bug reports for the top
line in the stack but found over 200 hits.

!ENTRY org.eclipse.jface 4 2 2005-04-14 13:24:50.737
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.AbstractMethodError: org/eclipse/jdt/core/IJavaElement.getElementType()I
	at org.eclipse.jdt.internal.core.JavaModelCache.getInfo(JavaModelCache.java:71)
	at
org.eclipse.jdt.internal.core.JavaModelManager.getInfo(JavaModelManager.java:886)
	at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:229)
	at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:217)
	at org.eclipse.jdt.internal.core.JavaElement.exists(JavaElement.java:136)
	at org.eclipse.jdt.internal.corext.refactoring.Checks.isAvailable(Checks.java:758)
	at
org.eclipse.jdt.internal.corext.refactoring.RefactoringAvailabilityTester.isPushDownAvailable(RefactoringAvailabilityTester.java:640)
	at
org.eclipse.jdt.internal.corext.refactoring.RefactoringAvailabilityTester.isPushDownAvailable(RefactoringAvailabilityTester.java:662)
	at
org.eclipse.jdt.internal.corext.refactoring.RefactoringAvailabilityTester.isPushDownAvailable(RefactoringAvailabilityTester.java:678)
	at
org.eclipse.jdt.ui.actions.PushDownAction.selectionChanged(PushDownAction.java:92)
	at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchSelectionChanged(SelectionDispatchAction.java:200)
	at
org.eclipse.jdt.ui.actions.SelectionDispatchAction.selectionChanged(SelectionDispatchAction.java:195)
	at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
	at
org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1021)
	at org.eclipse.core.runtime.Platform.run(Platform.java:757)
	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:40)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148)
	at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
	at
org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:1691)
	at
org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1359)
	at
org.eclipse.jdt.internal.ui.javaeditor.JavaOutlinePage.select(JavaOutlinePage.java:1194)
	at
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.synchronizeOutlinePage(JavaEditor.java:1883)
	at
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.synchronizeOutlinePage(JavaEditor.java:1870)
	at
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor.selectionChanged(JavaEditor.java:1953)
	at
org.eclipse.jdt.internal.ui.javaeditor.JavaEditor$EditorSelectionChangedListener.selectionChanged(JavaEditor.java:278)
	at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2295)
	at org.eclipse.jface.text.TextViewer.firePostSelectionChanged(TextViewer.java:2248)
	at org.eclipse.jface.text.TextViewer$4.run(TextViewer.java:2227)
	at org.eclipse.swt.widgets.Display.runTimer(Display.java:2936)
	at org.eclipse.swt.widgets.Display.messageProc(Display.java:2277)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:1625)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2525)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1570)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1534)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:306)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
	at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
	at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:228)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:156)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
	at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
	at java.lang.reflect.Method.invoke(Method.java:391)
	at org.eclipse.core.launcher.Main.invokeFramework(Main.java:315)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:268)
	at org.eclipse.core.launcher.Main.run(Main.java:942)
	at org.eclipse.core.launcher.Main.main(Main.java:926)
Comment 1 Philipe Mulet CLA 2005-04-14 15:16:59 EDT
Haven't heard about this issue so far. This feels too big to be true.
Could it be a corrupted JAR or bogus VM ?

Could you detail a bit more how you obtain it ? Which platform you are using ?
Comment 2 Kent Johnson CLA 2005-04-26 16:34:51 EDT
Please reopen after providing further information.

Which VM are you using?

Which platform/OS?
Comment 3 Tom Musta CLA 2005-04-26 16:47:44 EDT
I am running on Windows XP Professional using IBM JDK 1.4.2 (specifically, J2RE
1.4.2 IBM Windows 32 build cn142-20040717).  

The launch command is like this:

  eclipse.exe -vm c:\jdk14\java\jre\bin\javaw.exe -vmargs -Xj9

Comment 4 Tom Musta CLA 2005-04-26 16:51:58 EDT
Reopening ...
Comment 5 Kent Johnson CLA 2005-04-27 08:21:13 EDT
So you can repeat this problem fairly easily?

If so, can you try a different VM or turn off the jit to see if it still 
happens.
Comment 6 Tom Musta CLA 2005-04-27 09:15:53 EDT
Unfortunately, I cannot reproduce this at will.  However, it has happened to me
fairly regularly (maybe once every day or every other day).  It seems to happen
most frequently when I am actively editing code and the code is in some
syntactically invalid state (e.g. I haven't closed a brace ('}') or completed a
method name, etc.  

I will start by upgrading to a newer IBM JDK 1.4.2 and monitoring.  
Comment 7 Kent Johnson CLA 2005-04-28 04:44:33 EDT

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