为什么eclipse 3.0启动即退出

adherent

据说eclipse3。0做了不少改进，想升下级。原来的版本是2.1

启动后，弹出eclipse那个日蚀画面，选择workspace后，就保持在那个画面，能保持个五六分钟，然后piu一下就什么都没了。

以为咱机器配置差，cpu是847Mhz， 内存256M，玩不转3。0。 看了一下3。0的说明，用这个命令限制其只占用128M的内存，并选中本机的虚拟机
eclipse -vm e:\jdk1.4.2\jre\bin\javaw -vmargs -Xmx128M
状况一如从前。

这里的高手有没有什么建议？

GilbertLi

麻烦把相关的 LOG 贴出来

adherent

没有任何log文件产生出来。。。。。。

GilbertLi

在Workspace/.metadata下面有

adherent

log 信息如下
!SESSION Dez 09, 2004 20:39:35.74 ----------------------------------------------
eclipse.buildId=I200406251208
java.version=1.4.0-rc
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE

!ENTRY org.eclipse.ui 4 4 Dez 09, 2004 20:39:35.84
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 Dez 09, 2004 20:39:35.84
!MESSAGE java.lang.NullPointerException
!STACK 0
java.lang.NullPointerException
        at org.eclipse.ui.keys.KeyStroke.hashCode(KeyStroke.java:311)
        at java.util.HashMap.hash(HashMap.java:250)
        at java.util.HashMap.get(HashMap.java:301)
        at org.eclipse.ui.internal.commands.KeySequenceBindingNode.add(KeySequenceBindingNode.java:176)
        at org.eclipse.ui.internal.commands.KeySequenceBindingMachine.validateTree(KeySequenceBindingMachine.java:247)
        at org.eclipse.ui.internal.commands.KeySequenceBindingMachine.validateSolution(KeySequenceBindingMachine.java:226)
        at org.eclipse.ui.internal.commands.KeySequenceBindingMachine.getKeySequenceBindingsByCommandId(KeySequenceBindingMachine.java:78)
        at org.eclipse.ui.internal.commands.MutableCommandManager.calculateKeySequenceBindings(MutableCommandManager.java:238)
        at org.eclipse.ui.internal.commands.MutableCommandManager.readRegistry(MutableCommandManager.java:538)
        at org.eclipse.ui.internal.commands.MutableCommandManager.<init>(MutableCommandManager.java:192)
        at org.eclipse.ui.internal.commands.MutableCommandManager.<init>(MutableCommandManager.java:160)
        at org.eclipse.ui.internal.commands.CommandManagerFactory.getMutableCommandManager(CommandManagerFactory.java:34)
        at org.eclipse.ui.internal.commands.ws.WorkbenchCommandSupport.<init>(WorkbenchCommandSupport.java:261)
        at org.eclipse.ui.internal.Workbench.init(Workbench.java:766)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1325)
        at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
        at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
        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:183)
        at org.eclipse.core.launcher.Main.run(Main.java:644)
        at org.eclipse.core.launcher.Main.main(Main.java:628)

adherent

虚拟机升级到1。42就好了，晕

GilbertLi

好像虚拟机是老了一点，汗。