Failure causes high cpu utilization in eclipse 3.p

[GoogleCodeExporter]

!ENTRY org.eclipse.ui 4 0 2009-01-27 15:04:21.293
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable
(java.lang.NullPointerException)
        at org.eclipse.swt.SWT.error(SWT.java:3777)
        at org.eclipse.swt.SWT.error(SWT.java:3695)
        at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3342)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3071)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
        at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
        at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
        at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
        at
org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
        at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
        at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
        at
org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java
:113)
        at
org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ecli
pseAppLauncher.java:110)
        at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLau
ncher.java:79)
        at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
        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:39)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.jav
a:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
        at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Caused by: java.lang.NullPointerException
        at
com.googlecode.veloeclipse.editor.VelocityEditor.getHTMLElement(VelocityEditor.j
ava:381)
        at
com.googlecode.veloeclipse.editor.VelocityCompletionProcessor.getAttributesPropo
sals(VelocityCompletionProcessor.java:252)
        at
com.googlecode.veloeclipse.editor.VelocityCompletionProcessor.computeCompletionP
roposals(VelocityCompletionProcessor.java:186)
        at
org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals
(ContentAssistant.java:1836)
        at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(Co
mpletionProposalPopup.java:553)
        at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(Completio
nProposalPopup.java:550)
        at
org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionPro
posalPopup.java:485)
        at
org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
        at
org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(Compl
etionProposalPopup.java:479)
        at
org.eclipse.jface.text.contentassist.ContentAssistant$2.run(ContentAssistant.jav
a:377)
        at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
        at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
        ... 22 more

Original issue reported on code.google.com by kevin.ro...@gtempaccount.com on 27 Jan 2009 at 10:53

[GoogleCodeExporter]

Sorry, meant to type 3.4 but evidently I can't edit the issue after creation.

Original comment by kevin.ro...@gtempaccount.com on 27 Jan 2009 at 10:54

[GoogleCodeExporter]

Is there a consistent way to re-create this?

Original comment by byron.foster@gmail.com on 30 Jan 2009 at 4:21

[GoogleCodeExporter]

The code does not indicate which file it is failing on, or which element.  I 
would
suggest beefing up the error handling messages in this case so that it can be 
tracked
down when it happens again.

Original comment by kevin.ro...@gtempaccount.com on 30 Jan 2009 at 4:35

[GoogleCodeExporter]

Hi!

I also get this with veloeclipse 2.0.6.

In my case, this exception is thrown when trying to use autocomplete for html 
code (
autocompleting the available attributes for a div, for example). My Eclipse
environment is:

eclipse.buildId=M20080911-1700
java.version=1.6.0
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

The interesting thing is that on another machine I don't have this problem. This
problem started for me when I uninstalled and replaced the 
propsorter.sourceforge.net
plugin (v. 2.0.6) with the one from google code. I tried starting eclipse with 
-clean
but it didn't help.

Original comment by putypur...@gmail.com on 1 Feb 2009 at 4:00

[GoogleCodeExporter]

I believe this is now fixed in 2.0.7, please try and report back.

Original comment by byron.foster@gmail.com on 7 Feb 2009 at 4:51

[GoogleCodeExporter]

I've upgraded to 2.0.7 and the autocomplete works now.

Original comment by putypur...@gmail.com on 10 Feb 2009 at 6:49

[GoogleCodeExporter]

Original comment by byron.foster@gmail.com on 11 Feb 2009 at 8:24

• Changed state: Fixed