Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Memory Analyzer » The dreaded 'XPCOM error -2147467259'
The dreaded 'XPCOM error -2147467259' [message #758473] Wed, 23 November 2011 12:06 Go to next message
Dan Gravell is currently offline Dan GravellFriend
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(
at org.eclipse.swt.SWT.error(
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(
at org.eclipse.swt.widgets.Display.runAsyncMessages(
at org.eclipse.swt.widgets.Display.readAndDispatch(
at org.eclipse.ui.internal.Workbench.runEventLoop(
at org.eclipse.ui.internal.Workbench.runUI(
at org.eclipse.ui.internal.Workbench.access$4(
at org.eclipse.ui.internal.Workbench$
at org.eclipse.core.databinding.observable.Realm.runWithDefault(
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
at org.eclipse.mat.ui.rcp.Application.start(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.eclipse.equinox.launcher.Main.invokeFramework(
at org.eclipse.equinox.launcher.Main.basicRun(
at org.eclipse.equinox.launcher.Main.main(
Caused by: org.eclipse.swt.SWTError: XPCOM error -2147467259
at org.eclipse.swt.browser.Mozilla.error(
at org.eclipse.swt.browser.Mozilla.initXULRunner(
at org.eclipse.swt.browser.Mozilla.create(
at org.eclipse.swt.browser.Browser.<init>(
at org.eclipse.mat.ui.internal.panes.QueryTextResultPane.createPartControl(
at org.eclipse.mat.ui.editor.MultiPaneEditor.addPage(
at org.eclipse.mat.ui.editor.MultiPaneEditor.addPage(
at org.eclipse.mat.ui.editor.MultiPaneEditor.addNewPage(
at org.eclipse.mat.ui.QueryExecution.doDisplayResult(
at org.eclipse.mat.ui.QueryExecution.access$0(
at org.eclipse.mat.ui.QueryExecution$
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(
... 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 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, but that didn't work either.

It'd be great to get this working, Memory Analyzer is a useful tool!
Re: The dreaded 'XPCOM error -2147467259' [message #1007478 is a reply to message #758473] Wed, 06 February 2013 05:04 Go to previous message
rajeshwaran raja is currently offline rajeshwaran rajaFriend
Messages: 1
Registered: February 2013
Junior Member
I too getting this error...
Previous Topic:Live objects in MAT histogram?
Next Topic:Viewing Stackframes in hprof dumps
Goto Forum:

Current Time: Sat Jan 16 13:05:43 GMT 2021

Powered by FUDForum. Page generated in 0.01779 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top