Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Standard Widget Toolkit (SWT) » SWT browser not working with XULRunner 1.8.x, 1.9.x, 3.6.x, 10.x downloaded from mozilla.org(SWT browser not working with XULRunner 1.8.x, 1.9.x, 3.6.x, 10.x downloaded from mozilla.org)
SWT browser not working with XULRunner 1.8.x, 1.9.x, 3.6.x, 10.x downloaded from mozilla.org [message #896363] Wed, 18 July 2012 08:02 Go to next message
Mohsen Saboorian is currently offline Mohsen SaboorianFriend
Messages: 19
Registered: July 2009
Junior Member
Hi,
I'm using latest SWT 4.2 with an application in which I want to bundle XULRunner in order to deliver end user a portable application (our users always complain about setting MOZILLA_FIVE_HOME or other browser related issues on Linux). For this, I downloaded XULRunner from mozilla.org (h++p://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/) and passed the following jvm options: 
-Dorg.eclipse.swt.browser.XULRunnerPath=xulrunner (where xulrunner folder is available in my app)
-Dorg.eclipse.swt.browser.DefaultType=mozilla

Unfortunately I receive XPCOM error when I use any of 1.9, 3.6 and 10 xullrunners. When I remove the two options, it starts correctly as it finds a proper webkitgtk installation. This is fine, but I want it to work seamlessly on any Linux distribution even without webkitgtk.

My test platforms are Ubuntu 11.04 and 12.04, Sun JVM 1.7.03 32 bit, XULRunner 32bit 1.8.x, 1.9.x, 3.6.x, 10.x.

Thanks
Mohsen

[Updated on: Wed, 18 July 2012 08:07]

Report message to a moderator

Re: SWT browser do not work with XULRunner 1.8.x, 1.9.x, 3.6.x, 10.x downloaded from mozilla.org [message #896498 is a reply to message #896363] Wed, 18 July 2012 14:19 Go to previous messageGo to next message
Grant Gayed is currently offline Grant GayedFriend
Messages: 2150
Registered: July 2009
Senior Member
It sounds like you're doing the right thing, though you do not have to
set the org.eclipse.swt.browser.DefaultType property if you don't
strongly care which of the native renderers gets used (WebKitGTK is
tried first, but if it's not available then the fallback to a
mozilla-based renderer happens automatically).

If you're getting an XPCOM error then it sounds like it's finding a
XULRunner. What does the error's stack look like? Does the snippet at
www.eclipse.org/swt/faq.php#printmozillapath work for you (set its
org.eclipse.swt.browser.XULRunnerPath value with System.setProperty(...))?

Grant


On 7/18/2012 4:02 AM, Mohsen Saboorian wrote:
> Hi,
> I'm using latest SWT 4.2 with an application in which I want to bundle
> XULRunner in order to deliver end user a portable application (our users
> always complain about setting MOZILLA_FIVE_HOME or other browser related
> issues on Linux). For this, I downloaded XULRunner from mozilla.org
> (h++p://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/) and passed
> the following jvm options:
> -Dorg.eclipse.swt.browser.XULRunnerPath=xulrunner (where xulrunner
> folder is available in my app)
> -Dorg.eclipse.swt.browser.DefaultType=mozilla
>
> Unfortunately I receive XPCOM error when I use any of 1.9, 3.6 and 10
> xullrunners. When I remove the two options, it starts correctly as it
> finds a proper webkitgtk installation. This is fine, but I want it to
> work seamlessly on any Linux distribution even without webkitgtk.
>
> My test platforms are Ubuntu 11.04 and 12.04, Sun JVM 1.7.03 32 bit,
> XULRunner 32bit 1.8.x, 1.9.x, 3.6.x, 10.x.
>
> Thanks
> Mohsen

Report message to a moderator

Re: SWT browser do not work with XULRunner 1.8.x, 1.9.x, 3.6.x, 10.x downloaded from mozilla.org [message #896510 is a reply to message #896498] Wed, 18 July 2012 15:25 Go to previous messageGo to next message
Mohsen Saboorian is currently offline Mohsen SaboorianFriend
Messages: 19
Registered: July 2009
Junior Member
Thanks for the reply. Here is the output:


>>>Snippet creating SWT.MOZILLA-style Browser
XULRunner path: ./xulrunner/libxpcom.so
>>>This failed with the following error:
org.eclipse.swt.SWTError: XPCOM error 0x80520001
	at org.eclipse.swt.browser.Mozilla.error(Unknown Source)
	at org.eclipse.swt.browser.Mozilla.initXPCOM(Unknown Source)
	at org.eclipse.swt.browser.Mozilla.create(Unknown Source)
	at org.eclipse.swt.browser.Browser.<init>(Unknown Source)
	at DisplayMozillaVersion.main(DisplayMozillaVersion.java:14)


Snippet creating SWT.NONE-style Browser
XULRunner path: ./xulrunner/libxpcom.so
>>>This failed too, with the following error:
org.eclipse.swt.SWTError: XPCOM error 0x80520001
	at org.eclipse.swt.browser.Mozilla.error(Unknown Source)
	at org.eclipse.swt.browser.Mozilla.initXPCOM(Unknown Source)
	at org.eclipse.swt.browser.Mozilla.create(Unknown Source)
	at org.eclipse.swt.browser.Browser.<init>(Unknown Source)
	at DisplayMozillaVersion.main(DisplayMozillaVersion.java:21)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xb7741537, pid=5923, tid=3065842496
#
# JRE version: 7.0_05-b05
# Java VM: Java HotSpot(TM) Client VM (23.1-b03 mixed mode linux-x86 )
# Problematic frame:
# C  [ld-linux.so.2+0x9537]  _dl_rtld_di_serinfo+0xa17
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/mohsen/Desktop/zekr-portable/hs_err_pid5923.log
#
# If you would like to submit a bug report, please visit:
#   h++p://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)

Report message to a moderator

icon14.gif  Re: SWT browser do not work with XULRunner 1.8.x, 1.9.x, 3.6.x, 10.x downloaded from mozilla.org [message #896795 is a reply to message #896498] Thu, 19 July 2012 20:14 Go to previous message
Mohsen Saboorian is currently offline Mohsen SaboorianFriend
Messages: 19
Registered: July 2009
Junior Member
The problem resolved by specifying full path of the XULRunner after the propertye: 
org.eclipse.swt.browser.XULRunnerPath
. I believe this is a bug, and Eclipse should also accept relative paths. Please specify this trick in SWQ FAQ page until it's resolved in future releases.

Thanks.

Report message to a moderator

Previous Topic:SWT at the ARM , Linux
Next Topic:Wrong font on Eclipse Juno Editor Tabs
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Fri Apr 19 04:07:07 GMT 2024

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

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

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly