Bug 6587 - Fail to use Eclipse Java editor, somtimes crush as well.
Summary: Fail to use Eclipse Java editor, somtimes crush as well.
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows NT
: P1 blocker (vote)
Target Milestone: ---   Edit
Assignee: Kai-Uwe Maetzel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-05 09:59 EST by David Maroshi CLA
Modified: 2002-02-06 06:13 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Maroshi CLA 2001-12-05 09:59:47 EST
Installed Ecpipse build 20011107, then 20011129 is not opening at all.
Using JDK 1.3.1 on windows nt service pack 5.
the stroty:

Open eclipse OK,
Create a new Java project OK,
Create a new Java package OK,
Create new java class (derived from Object) "HelloWorld" FAil 
with failure notice,
Opening  the newly created HelloWorld class Fail.
Now trying to read the attached error log creates a new error each time 
closeing the error log property window with OK.

=======================================================
Here is a copy of the error stack:


org.eclipse.swt.SWTException: Failed to execute runnable 
(java.lang.NullPointerException)
	at org.eclipse.swt.SWT.error(SWT.java:1846)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
(Synchronizer.java:96)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1342)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1170)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:727)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:710)
	at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:820)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
	at org.eclipse.core.launcher.Main.run(Main.java:502)
	at org.eclipse.core.launcher.Main.main(Main.java:362)

Unhandaled exception cought in event loop:

Problem when invoking code from plug-in: org.eclipse.ui

java.lang.NoSuchMethodError
	at org.eclipse.jdt.internal.debug.ui.display.EvaluateAction.getContext
(EvaluateAction.java:81)
	at 
org.eclipse.jdt.internal.debug.ui.display.EvaluateAction.isValidStackFrame
(EvaluateAction.java:201)
	at org.eclipse.jdt.internal.debug.ui.display.EvaluateAction.update
(EvaluateAction.java:185)
	at 
org.eclipse.jdt.internal.debug.ui.display.EvaluateAction.setActiveEditor
(EvaluateAction.java:346)
	at org.eclipse.ui.internal.EditorPluginAction.editorChanged
(EditorPluginAction.java:65)
	at org.eclipse.ui.internal.EditorPluginAction.<init>
(EditorPluginAction.java:29)
	at org.eclipse.ui.internal.ActionDescriptor.createAction
(ActionDescriptor.java:141)
	at org.eclipse.ui.internal.ActionDescriptor.<init>
(ActionDescriptor.java:105)
	at org.eclipse.ui.internal.ViewerActionBuilder.createActionDescriptor
(ViewerActionBuilder.java:33)
	at org.eclipse.ui.internal.PluginActionBuilder.readElement
(PluginActionBuilder.java:292)
	at org.eclipse.ui.internal.registry.RegistryReader.readElements
(RegistryReader.java:119)
	at org.eclipse.ui.internal.registry.RegistryReader.readElementChildren
(RegistryReader.java:109)
	at org.eclipse.ui.internal.PluginActionBuilder.readElement
(PluginActionBuilder.java:298)
	at org.eclipse.ui.internal.registry.RegistryReader.readElements
(RegistryReader.java:119)
	at org.eclipse.ui.internal.registry.RegistryReader.readExtension
(RegistryReader.java:128)
	at org.eclipse.ui.internal.registry.RegistryReader.readRegistry
(RegistryReader.java:140)
	at org.eclipse.ui.internal.PluginActionBuilder.readContributions
(PluginActionBuilder.java:265)
	at org.eclipse.ui.internal.ViewerActionBuilder.readViewerContributions
(ViewerActionBuilder.java:53)
	at org.eclipse.ui.internal.PopupMenuExtender.readStaticActions
(PopupMenuExtender.java:76)
	at org.eclipse.ui.internal.PopupMenuExtender.<init>
(PopupMenuExtender.java:39)
	at org.eclipse.ui.internal.PartSite.registerContextMenu
(PartSite.java:151)
	at org.eclipse.ui.texteditor.AbstractTextEditor.createPartControl
(AbstractTextEditor.java:810)
	at 
org.eclipse.jdt.internal.ui.javaeditor.CompilationUnitEditor.createPartControl
(CompilationUnitEditor.java:876)
	at org.eclipse.ui.internal.PartPane$2.run(PartPane.java:53)
	at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:812)
	at org.eclipse.core.runtime.Platform.run(Platform.java:395)
	at org.eclipse.ui.internal.PartPane.createChildControl(PartPane.java:51)
	at org.eclipse.ui.internal.PartPane.createControl(PartPane.java:93)
	at org.eclipse.ui.internal.EditorWorkbook.createPage
(EditorWorkbook.java:183)
	at org.eclipse.ui.internal.EditorWorkbook.add(EditorWorkbook.java:75)
	at org.eclipse.ui.internal.EditorArea.addEditor(EditorArea.java:43)
	at org.eclipse.ui.internal.EditorPresentation.openEditor
(EditorPresentation.java:292)
	at org.eclipse.ui.internal.EditorManager$2.run(EditorManager.java:451)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:56)
	at org.eclipse.ui.internal.EditorManager.openInternalEditor
(EditorManager.java:437)
	at org.eclipse.ui.internal.EditorManager.openInternalEditor
(EditorManager.java:490)
	at org.eclipse.ui.internal.EditorManager.openEditor
(EditorManager.java:362)
	at org.eclipse.ui.internal.EditorManager.openEditor
(EditorManager.java:265)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor
(WorkbenchPage.java:1063)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor
(WorkbenchPage.java:966)
	at org.eclipse.jdt.internal.ui.wizards.NewElementWizard$1.run
(NewElementWizard.java:57)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:29)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages
(Synchronizer.java:93)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1342)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1170)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:727)
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:710)
	at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:820)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
	at org.eclipse.core.launcher.Main.run(Main.java:502)
	at org.eclipse.core.launcher.Main.main(Main.java:362)

Joy and happines
David

Hope this helps.
I am currently putting my hands away from eclipse.
Comment 1 Erich Gamma CLA 2001-12-05 10:50:42 EST
Nobody else has reported this problem.
I suspect you are using a daily build instead of a stable build
are you using the integration builds? 

Please try the stable build from tomorrow again.
Comment 2 Wolfgang Frech CLA 2001-12-12 07:22:31 EST
The Java editor crashes when I type the first character in a generated class
template in a position where it is the beginning of a identifier or a keyword.
On the other hand, "//"-comments or javadoc-comments with characters inside the
comment, or ";"-characters in method bodies are ok, no crash with that.
Crash means: no reaction, freezing for a few seconds, than exiting without any
message.

Repeatable.

My installation is R1.0 (eclipse-platform-R1.0-win32.zip,
eclipse-JDT-R1.0-win32.zip) and Sun's JRE 1.3.0_01 on Win2k.

Definitely _no_ dayly build of eclipse.
Comment 3 Erich Gamma CLA 2001-12-12 08:29:41 EST
The first walkback below is from a broken daily build and is not valid.

Wolfgang please provide detailed steps in bug, e.g.,
1) create a new class
2) insert a template
3) move the cursor and type
->...

Was there any information in the .log file?
Comment 4 Wolfgang Frech CLA 2001-12-12 11:22:13 EST
situation before:
workspace (zip attached) with one Java project, one package oneclass, one class
OneClass.

1) click link to eclipse.exe on Windows desktop
2) splash screen shows
3) Java - Eclipse Project SDK shows, view Packages
project OneClass expanded one level: package oneclass and JRE_LIB with
C:\[...]\rt.jar
4) click to expand package oneclass
5) class source One.java shows
6) doubleclick to open class source One.java
7) editor One.java and Outline show
8) click to set caret in body of class One in empty line
9) caret shows at the beginning of empty line
10) type "// harmless" (without quotes)
11) text shows
12) [...]\eclipse\workspace\.metadata\.plugins\org.eclipse.help.ui\.log is empty
13) click to set caret at end of line "// harmless"
14) enter "[RETURN]a²
15) eclipse freezes and vanishes
16) [...]\eclipse\workspace\.metadata\.plugins\org.eclipse.help.ui\.log is still
empty
Comment 5 Wolfgang Frech CLA 2001-12-17 09:54:44 EST
Works for me, now; might work for David (original reporter).

Cause: use of unsupported VM, installed as default VM
Solution: use a supported VM
Detail:
If you have more than one JRE/JDK installed, and if you are not sure, which one
is the default, make sure that you start the eclipse application with an
explicit -vm flag for a required 1.2 or 1.3 level VM.

Example for startup command script:
# eclipse_jre13.cmd
.\eclipse.exe -vm C:\programme\javasoft\jre\1.3.0_01\bin\javaw.exe

Feature request:
Eclipse could check for and warn about unsupported VM-version during start-up.
Comment 6 Kai-Uwe Maetzel CLA 2002-02-06 06:13:31 EST
Marked as Invalid because of provided explanation. Pls. log separat DCR for VM 
probe feature.