Eclipse Community Forums: Memory Analyzer » The dreaded 'XPCOM error -2147467259'

Help

Home

Home » Eclipse Projects » Memory Analyzer » The dreaded 'XPCOM error -2147467259'

Show: Today's Messages :: Show Polls :: Message Navigator

The dreaded 'XPCOM error -2147467259' [message #758473]

Wed, 23 November 2011 12:06

Dan Gravell

Messages: 4
Registered: November 2011

Junior Member

I'm on Xubuntu 11.10, 64 bit.

I can run Memory Analyzer, and I can create the Dominator Tree. However, other views such as Leak Suspects and Top Components fail with the following error in the error log:

org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTError: XPCOM error -2147467259)
at org.eclipse.swt.SWT.error(SWT.java:4083)
at org.eclipse.swt.SWT.error(SWT.java:3998)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.mat.ui.rcp.Application.start(Application.java:26)
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:369)
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:620)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
Caused by: org.eclipse.swt.SWTError: XPCOM error -2147467259
at org.eclipse.swt.browser.Mozilla.error(Mozilla.java:2414)
at org.eclipse.swt.browser.Mozilla.initXULRunner(Mozilla.java:2377)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:641)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:119)
at org.eclipse.mat.ui.internal.panes.QueryTextResultPane.createPartControl(QueryTextResultPane.java:72)
at org.eclipse.mat.ui.editor.MultiPaneEditor.addPage(MultiPaneEditor.java:585)
at org.eclipse.mat.ui.editor.MultiPaneEditor.addPage(MultiPaneEditor.java:574)
at org.eclipse.mat.ui.editor.MultiPaneEditor.addNewPage(MultiPaneEditor.java:496)
at org.eclipse.mat.ui.QueryExecution.doDisplayResult(QueryExecution.java:294)
at org.eclipse.mat.ui.QueryExecution.access$0(QueryExecution.java:234)
at org.eclipse.mat.ui.QueryExecution$1.run(QueryExecution.java:138)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
... 23 more

Searching on the Web suggests this is something to do with xulrunner. My xulrunner in /usr/lib/xulrunner has only a plugins/ directory and no libxpcom.so. So I tried downloading one of the releases from Mozilla and set the org.eclipse.swt.browser.XULRunnerPath to the new location, which does have a libxpcom.so, but that didn't work either.

It'd be great to get this working, Memory Analyzer is a useful tool!

Report message to a moderator