Community
Participate
Working Groups
Following exception occurs over and over again while child Eclipse of 4.2 Eclipse M1 is up and running. I am running on a F14 i686 system and am using Fedora openjdk 1.6.0. I also have the Linux tools plug-in and CDT plug-in projects checked out (via egit) in the parent Eclipse. The NPE loop occurs before I do anything in the child workspace and continues on and on even while things seem to work ok in the child Eclipse. java.lang.NullPointerException at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.generateParameterizedCommand(HandledContributionItem.java:504) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.getToolTipText(HandledContributionItem.java:472) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.updateToolItem(HandledContributionItem.java:457) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.update(HandledContributionItem.java:403) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.update(HandledContributionItem.java:390) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$2.run(HandledContributionItem.java:179) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.updateItemEnablement(HandledContributionItem.java:205) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$ToolItemUpdateTimer.run(HandledContributionItem.java:123) at org.eclipse.swt.widgets.Display.timerProc(Display.java:4154) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2258) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:969) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:885) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:90) at org.eclipse.ui.internal.Workbench$3.run(Workbench.java:539) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:519) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Did you start with a Juno EPP package or a regular 4.2 build, Jeff? What is the name of the file you downloaded?
(In reply to comment #1) > Did you start with a Juno EPP package or a regular 4.2 build, Jeff? What is the > name of the file you downloaded? eclipse-SDK-4.2M1-linux-gtk.tar.gz
(In reply to comment #2) > eclipse-SDK-4.2M1-linux-gtk.tar.gz What plug-ins do you have installed besides EGit, Jeff? You mention having plug-ins checked out from Git but are they also installed on your Eclipse instance?
(In reply to comment #3) > (In reply to comment #2) > > eclipse-SDK-4.2M1-linux-gtk.tar.gz > > What plug-ins do you have installed besides EGit, Jeff? You mention having > plug-ins checked out from Git but are they also installed on your Eclipse > instance? I have linux tools plug-ins checked out: git://git.eclipse.org/gitroot/linuxtools/org.eclipse.linuxtools.git I closed all the test plug-ins, didn't bother with releng plug-ins and closed the lttng plug-ins so that there were no errors (except missing ABI baseline). I also have the CDT checked out: git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git again, sans test plug-ins and for platform-specific plug-ins, just my own platform (linux x86)
Created attachment 209632 [details] error-log form starting email-sample
I just ran into the same error. What I did: 1. Download Eclipse 4.2M4 Classic (happened on M1 too) 2. Create the mail-demo-application for eclipse 3.7 3. Follow guide at [1] in order to make it run in 4.x [1] http://tomsondev.bestsolution.at/2011/07/01/eclipse-4-1-run-your-3-x-rcp-in-4-1/ I run Linux Mint 12 (~Ubuntu 11.10). I tried openjdk-1.6.0_23, openjdk-1.7.0_147-icedtea and sun-java 1.6.0_26 all with the same result.
(In reply to comment #6) > I just ran into the same error. I cannot reproduce the problem although I am on Windows 7. Could you debug and try to see which command the contribution item is trying to use? What is the id of the model item?
It was happending with test.plugin.open (with test.plugin being the projects name). For some reason I cannot reproduce the problem anymore... It may be related to some OS-software-update. Also a corrupted runtime-workspace might have been a problem. I tried various combinations of eclipse 4.1 and 4.2M2 in order to reproduce the problem, but I'm not able to anymore :(
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
