[Slackbuilds-users] [FIX] Eclipse + xulrunner issue.

[Luis Henrique]

On 06/17/2010 06:47 PM, Antonio Hernández Blas wrote:
> Hi all.
>
> There's an issue with Eclipse and it's internal web browser that cause
> a fatal error with the Java VM. When you launch eclipse you may get a
> message like these ones:
>
> This one is from my system (slackware 13.0 + jdk 6u16 + firefox 3.6.3):
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0xb2ffe82f, pid=6504, tid=3085474000
> #
> # JRE version: 6.0_16-b01
> # Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode, sharing linux-x86 )
> # Problematic frame:
> # C  [libxpcom_core.so+0x8882f]
> #
> # An error report file with more information is saved as:
> # $HOME/hs_err_pid6504.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
> /usr/bin/eclipse: line 3:  6504 Aborted                 /opt/eclipse/eclipse $@
>
> This one is from Howard Pepper's system (slackware 13.1 + jdk 6u20 +
> firefox 3.6.3):
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0xb212eb00, pid=14285, tid=3076683456
> #
> # JRE version: 6.0_20-b02
> # Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing linux-x86 )
> # Problematic frame:
> # C  [libxul.so+0xa7ab00]
> #
> # An error report file with more information is saved as:
> # $HOME/hs_err_pid14285.log
> #
> # If you would like to submit a bug report, please visit:
> #   http://java.sun.com/webapps/bugreport/crash.jsp
> #
> /usr/bin/eclipse: line 3: 14285 Aborted /opt/eclipse/eclipse $@
>
> Fixes:
>
> You can "simple" install xulrunner:
> http://slackbuilds.org/repository/13.0/libraries/xulrunner/
> http://slackbuilds.org/repository/13.1/libraries/xulrunner/
>
> But build this package takes quite a lot of time.
>
> The second fix (that doesn't require to install xulrunner but
> seamonkey) is to specify to the Java VM the location of xulrunner
> (http://www.eclipse.org/swt/faq.php#specifyxulrunner). To make this
> edit
> /opt/eclipse/eclipse.ini
> and add the line:
> -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/seamonkey
> below the '-vmargs' line.
>
> Note: xulrunner is also inside /usr/lib/firefox, but if you specify
> this, you would get a message like:
>
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0xb80ab31d, pid=28349, tid=3086207184
> #
> # JRE version: 6.0_16-b01
> # Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode, sharing linux-x86 )
> # Problematic frame:
> # C  [libpthread.so.0+0xa31d]  pthread_cond_signal+0xd
> #
> # An error report file with more information is saved as:
> # $HOME/hs_err_pid28349.log
> /opt/eclipse/eclipse: symbol lookup error:
> /usr/lib/firefox-3.6.3/libxul.so: undefined symbol:
> _Z20js_NextActiveContextP9JSRuntimeP9JSContext
>
> This was just tested in an x86 system, i' don't know if this applied
> to x86_64 too and BTW, this is not related to /etc/ld.so.conf
> misconfiguration or anything like that.
>
> Thanks to Howard Pepper for reminding me about this issue.
>
> Any comment is welcome :)
>

Wouldn't you know, this also fixes RSSOwl! I added:

 > -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/seamonkey

just below the '-vmargs' line in the /usr/lib/RSSOwl/RSSOwl.ini file, 
and then it never crashed again :)

This really should be made into a patch and/or README information on the 
RSSOwl slackbuild.

Thanks, Antonio!

-- Luis