Bug 30786 java.lang.NoSuchFieldError: handle
Using Eclipse in Linux with Build id: 200302020010 i occasionally get strange errors which prevents modified Java-files from being saved. Happens randomly but when starting to appear stays until the file is removed editor and after reopening saving works ok (for awhile). Notice the same behaviour in maybe build 20030201. Build 2901 (ddmm) doesn't suffer from this bug. Here's the .log: !ENTRY org.eclipse.ui 4 4 helmi 03, 2003 03:49:34.516 !MESSAGE Unhandled exception caught in event loop. !ENTRY org.eclipse.ui 4 0 helmi 03, 2003 03:49:34.607 !MESSAGE handle !STACK 0 java.lang.NoSuchFieldError: handle at org.eclipse.jdt.internal.ui.javaeditor.JavaMarkerAnnotation.getImage(JavaMarkerAnnotation.java:267) at org.eclipse.ui.texteditor.MarkerAnnotation.paint(MarkerAnnotation.java:196) at org.eclipse.jface.text.source.AnnotationRulerColumn.doPaint(AnnotationRulerColumn.java:350) at org.eclipse.jface.text.source.AnnotationRulerColumn.doubleBufferPaint(AnnotationRulerColumn.java:241) at org.eclipse.jface.text.source.AnnotationRulerColumn.access$3(AnnotationRulerColumn.java:216) at org.eclipse.jface.text.source.AnnotationRulerColumn$1.paintControl(AnnotationRulerColumn.java:155) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:80) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:77) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:897) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:922) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:906) at org.eclipse.swt.widgets.Control.gtk_expose_event(Control.java:1618) at org.eclipse.swt.widgets.Composite.gtk_expose_event(Composite.java:322) at org.eclipse.swt.widgets.Canvas.gtk_expose_event(Canvas.java:101) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1138) at org.eclipse.swt.widgets.Display.windowProc(Display.java:1844) at org.eclipse.swt.internal.gtk.OS.gtk_main_iteration(Native Method) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1255) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1265) at org.eclipse.ui.internal.Workbench.run(Workbench.java:1248) at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:845) at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) 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) I tried looking for an existing bug but didn't find one, so i decided to make a new one.
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/javaeditor/JavaMarkerAnnotation.java
}
	
	/*
	 * @see IJavaAnnotation#getArguments()
	 */
	public String[] getArguments() {
		if (isProblem())
			return Util.getProblemArgumentsFromMarker(getMarker().getAttribute(IJavaModelMarker.ARGUMENTS, "")); 
		return null;
	}
	/*
	 * @see IJavaAnnotation#getId()
	 */
	public int getId() {
		if (isProblem())
			return getMarker().getAttribute(IJavaModelMarker.ID, -1);
		return -1;
	}
	
	/*
	 * @see IJavaAnnotation#isProblem()
	 */
	public boolean isProblem() {
		return fType == AnnotationType.WARNING || fType == AnnotationType.ERROR;
	}
	
	/*
	 * @see IJavaAnnotation#isRelevant()
	 */
	public boolean isRelevant() {