Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 370959

Summary:	'Animation Start' has encountered a problem (on launch)
Product:	z_Archived	Reporter:	Dennis Sänger <eclipse>
Component:	PDT	Assignee:	PHP Core <php.core-inbox>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	dpavliuchenko, jacek.pospychala, silviya, wywrzal
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Dennis Sänger

2012-02-08 09:48:11 EST

Overview:

Every time I try to run/debug a file or using an external tool configuration I get the following error message:

PROBLEM OCCURRED
'Animation start' has encountered a problem.
An internal error has occurred.

The error occurs since PDT 3.0.2 was installed, even when launching other files in other perspectives (e.g. a Java/JUnit program).

Steps to Reproduce:

Launch an arbitrary file in eclipse

Build Date & Platform:

Eclipse Indigo Build id: 20110916-0149 with PDT 3.0.2
MacOSX 10.6.8


Additional Information:

See: http://www.eclipse.org/forums/index.php/m/793767/#msg_793767

Comment 1 Greg Amerson

2012-06-06 06:45:42 EDT

Possible workaround...

I recently ran into this same problem with my own custom eclipse product distribution (custom name, custom .app folder, etc).  The problem I had was this setting in the .ini file:[code]-Xdock:icon=../Resources/Eclipse.icns[/code] was pointing to a non-existent file (there was no ../Resources/Eclipse.icns in my custom product, the .icns file had another custom name. 

So in your PDT installation on OSX open up the .app folder and then dig down into MacOS/Contents and look at the .ini file.  make sure that the -Xdock:icon property is pointing to a valid/existing file.  If you don't have that property then add it.  Then relaunch Eclipse/PDT and try again.

Comment 2 Dennis Sänger

2012-06-13 08:39:40 EDT

> So in your PDT installation on OSX open up the .app folder and then dig down
> into MacOS/Contents and look at the .ini file.  make sure that the -Xdock:icon
> property is pointing to a valid/existing file.  If you don't have that property
> then add it.  Then relaunch Eclipse/PDT and try again.

Thanks for your comment, but that was not the problem in my case.

Comment 3 Michal Niewrzal

2016-06-08 18:01:54 EDT

Issue is old with no log or additional info.

Comment 4 Sylvia Tancheva

2016-06-27 08:06:26 EDT

Closing. Please reopen with more recent/relevant information if still reproducible.

Comment 5 Dmytro Pavliuchenko

2017-01-13 18:18:46 EST

I'm using Red Hat JBoss Developer Studio and experiencing the same issue
Version: 10.2.0.GA
Build id: GA-v20161125-1418-B55
Build date: 20161125-1418

Under the hoods it is the Eclipse Platform
Version: 4.6.1.v20160907-1200
Build id: M20160907-1200

In the Error log there is the following message:

eclipse.buildId=10.2.0.GA-v20161125-1418-B55
java.version=1.8.0_74
java.vendor=Oracle Corporation
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=fr_FR
Framework arguments:  -product com.jboss.devstudio.core.product -keyring /Users/dmytro/.eclipse_keyring
Command-line arguments:  -os macosx -ws cocoa -arch x86_64 -product com.jboss.devstudio.core.product -keyring /Users/dmytro/.eclipse_keyring

org.eclipse.ui
Error
Thu Jan 12 23:47:37 CET 2017
An internal error has occurred.

java.lang.NullPointerException
	at org.eclipse.swt.widgets.TaskItem.updateImage(TaskItem.java:426)
	at org.eclipse.swt.widgets.TaskItem.setProgressState(TaskItem.java:395)
	at org.eclipse.ui.internal.progress.TaskBarProgressManager$2.setProgressState(TaskBarProgressManager.java:129)
	at org.eclipse.ui.internal.progress.TaskBarProgressManager$2.runInUIThread(TaskBarProgressManager.java:103)
	at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1519)