CSS crash by clicking on a help web link (Linux xulrunner, webkit version incompatibility) #388

Open
charlesHenryPATARD opened this Issue Feb 19, 2014 · 11 comments

Comments

Projects
None yet
3 participants
@charlesHenryPATARD
Contributor

charlesHenryPATARD commented Feb 19, 2014

When I clic on w3schools JS Tutorial link in CSS help and only this link CSS crash.
helpcrash

@charlesHenryPATARD

This comment has been minimized.

Show comment
Hide comment
@charlesHenryPATARD

charlesHenryPATARD Feb 19, 2014

Contributor

You can see the error below :

"#
"# A fatal error has been detected by the Java Runtime Environment:
"#
"# SIGSEGV (0xb) at pc=0x0000000000000002, pid=6377, tid=140392036443904
"#
"# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
"# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 "compressed oops)
"# Problematic frame:
"# C 0x0000000000000002
"#
"# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit "-c unlimited" before starting Java again
"#
"# If you would like to submit a bug report, please visit:
"# http://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.
"#
We used this environnement
Linux 2.6.32-358.6.2.el6.x86_64 x86_64
Eclipse RCP version 3.8

Is anyone ever see this crash ?

Contributor

charlesHenryPATARD commented Feb 19, 2014

You can see the error below :

"#
"# A fatal error has been detected by the Java Runtime Environment:
"#
"# SIGSEGV (0xb) at pc=0x0000000000000002, pid=6377, tid=140392036443904
"#
"# JRE version: Java(TM) SE Runtime Environment (7.0_45-b18) (build 1.7.0_45-b18)
"# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08 mixed mode linux-amd64 "compressed oops)
"# Problematic frame:
"# C 0x0000000000000002
"#
"# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit "-c unlimited" before starting Java again
"#
"# If you would like to submit a bug report, please visit:
"# http://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.
"#
We used this environnement
Linux 2.6.32-358.6.2.el6.x86_64 x86_64
Eclipse RCP version 3.8

Is anyone ever see this crash ?

@kasemir

This comment has been minimized.

Show comment
Hide comment
@kasemir

kasemir Feb 19, 2014

Contributor

Yes, I see that too.

I use RedHat 6, also 64 bit. But we use Eclipse 3.7.2 as the target platform, not 3.8.

It's fine with Mac OS X.
It's also fine on a Linux computer that cannot reach the w3schools tutorial because of a firewall.

So the issue is in those w3schools web pages.

The crash dump that you post should also include a line
"An error report file with more information is saved as: ../hs_err_pid23143.log",
and if you look in there, I find a stack trace with /usr/lib64/libwebkit-1.0.so.2

In the past, we have seen crashes on Linux related to the web browser integration. This would also happen with tool-tips because they somehow try to use a web browser library to render their content.
In the past, that mean installing chromium or different versions of firefox.

Workaround: Use Python (jython) scripts, or only JavaScript syntax that you already know, so you avoid the w3schools web site ;-)

Contributor

kasemir commented Feb 19, 2014

Yes, I see that too.

I use RedHat 6, also 64 bit. But we use Eclipse 3.7.2 as the target platform, not 3.8.

It's fine with Mac OS X.
It's also fine on a Linux computer that cannot reach the w3schools tutorial because of a firewall.

So the issue is in those w3schools web pages.

The crash dump that you post should also include a line
"An error report file with more information is saved as: ../hs_err_pid23143.log",
and if you look in there, I find a stack trace with /usr/lib64/libwebkit-1.0.so.2

In the past, we have seen crashes on Linux related to the web browser integration. This would also happen with tool-tips because they somehow try to use a web browser library to render their content.
In the past, that mean installing chromium or different versions of firefox.

Workaround: Use Python (jython) scripts, or only JavaScript syntax that you already know, so you avoid the w3schools web site ;-)

@charlesHenryPATARD

This comment has been minimized.

Show comment
Hide comment
@charlesHenryPATARD

charlesHenryPATARD Feb 20, 2014

Contributor

I have found a solution. The carsh was due to the version of xulrunner. Eclipse need to use a version smaller than 2.0.
You need to install the library and add those vm args to your product :
-Dorg.eclipse.swt.browser.XULRunnerPath=/path/to/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla

Link to download the library
http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/03/2012-03-02-03-32-11-mozilla-1.9.2/xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar.bz2

Eclipse 3.7 can't use a version beyond 2.0 of xulrunner. May be eclipse 4.x ?

Contributor

charlesHenryPATARD commented Feb 20, 2014

I have found a solution. The carsh was due to the version of xulrunner. Eclipse need to use a version smaller than 2.0.
You need to install the library and add those vm args to your product :
-Dorg.eclipse.swt.browser.XULRunnerPath=/path/to/xulrunner
-Dorg.eclipse.swt.browser.DefaultType=mozilla

Link to download the library
http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/03/2012-03-02-03-32-11-mozilla-1.9.2/xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar.bz2

Eclipse 3.7 can't use a version beyond 2.0 of xulrunner. May be eclipse 4.x ?

@kasemir

This comment has been minimized.

Show comment
Hide comment
@kasemir

kasemir Feb 20, 2014

Contributor

Execllent!
Yes, 'xulrunner' is the library used by SWT to call the web browser on
Linux.

Not sure if Eclipse 4 changes much. Eclipse 3 vs. 4 has different code on
top of SWT. The "RCP" support of Eclipse 3 has been replaced/updated with a
model-based GUI, and a compatibility layer to allow existing RCP code. The
SWT code is pretty much the same for both.

Thanks,
Kay

On Thu, Feb 20, 2014 at 3:07 AM, charlesHenryPATARD <
notifications@github.com> wrote:

I have found a solution. ...

Eclipse 3.7 can't use a version beyond 2.0 of xulrunner. May be eclipse 4.x
?

Contributor

kasemir commented Feb 20, 2014

Execllent!
Yes, 'xulrunner' is the library used by SWT to call the web browser on
Linux.

Not sure if Eclipse 4 changes much. Eclipse 3 vs. 4 has different code on
top of SWT. The "RCP" support of Eclipse 3 has been replaced/updated with a
model-based GUI, and a compatibility layer to allow existing RCP code. The
SWT code is pretty much the same for both.

Thanks,
Kay

On Thu, Feb 20, 2014 at 3:07 AM, charlesHenryPATARD <
notifications@github.com> wrote:

I have found a solution. ...

Eclipse 3.7 can't use a version beyond 2.0 of xulrunner. May be eclipse 4.x
?

@kasemir

This comment has been minimized.

Show comment
Hide comment
@kasemir

kasemir Feb 25, 2014

Contributor

I think we can close the issue since there's nothing we can do to the CSS sources about this.

Still, it's important that we somehow find this issue and the fix if somebody later wonders about this crash. So I've updated the title to include "xulrunner" and "webkit". So next time somebody gets a crash with "webkit" in the stack trace, maybe that makes it fairly easy to find this issue.

Contributor

kasemir commented Feb 25, 2014

I think we can close the issue since there's nothing we can do to the CSS sources about this.

Still, it's important that we somehow find this issue and the fix if somebody later wonders about this crash. So I've updated the title to include "xulrunner" and "webkit". So next time somebody gets a crash with "webkit" in the stack trace, maybe that makes it fairly easy to find this issue.

@berryma4

This comment has been minimized.

Show comment
Hide comment
@berryma4

berryma4 Feb 25, 2014

Member

Which branch is this on?

Member

berryma4 commented Feb 25, 2014

Which branch is this on?

@kasemir

This comment has been minimized.

Show comment
Hide comment
@kasemir

kasemir Mar 4, 2014

Contributor

I don't think the branch matters. Anything built against the 3.7.2 target architecture will have problems on certain Linux setups, because of the issue with the SWT web integration and certain versions of xulrunner/webkit.

Contributor

kasemir commented Mar 4, 2014

I don't think the branch matters. Anything built against the 3.7.2 target architecture will have problems on certain Linux setups, because of the issue with the SWT web integration and certain versions of xulrunner/webkit.

@kasemir

This comment has been minimized.

Show comment
Hide comment
@kasemir

kasemir Mar 4, 2014

Contributor

Here's the fix as a recipe

... since we can't do anything about it in the CSS sources at this time.
Well, we could include the xulrunner binaries, but it's only required for certain Linux releases and might cause trouble on others, so it might be best left as a local Linux admin task when installing CSS.

If you get CSS crashes which point to libwebkit when trying to access online help, embedded web displays, maybe even tool-tips:

wget http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/03/2012-03-02-03-32-11-mozilla-1.9.2/xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar.bz2
bzip2 -d xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar.bz2
tar vxf xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar

Then add the following to either the css .... -vmargs ... command line or your product's css.ini file:

-Dorg.eclipse.swt.browser.DefaultType=mozilla -Dorg.eclipse.swt.browser.XULRunnerPath=/path/to/unpacked/xulrunner

That path is the path to the unpacked xulrunner directory.

Contributor

kasemir commented Mar 4, 2014

Here's the fix as a recipe

... since we can't do anything about it in the CSS sources at this time.
Well, we could include the xulrunner binaries, but it's only required for certain Linux releases and might cause trouble on others, so it might be best left as a local Linux admin task when installing CSS.

If you get CSS crashes which point to libwebkit when trying to access online help, embedded web displays, maybe even tool-tips:

wget http://ftp.mozilla.org/pub/mozilla.org/xulrunner/nightly/2012/03/2012-03-02-03-32-11-mozilla-1.9.2/xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar.bz2
bzip2 -d xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar.bz2
tar vxf xulrunner-1.9.2.28pre.en-US.linux-x86_64.tar

Then add the following to either the css .... -vmargs ... command line or your product's css.ini file:

-Dorg.eclipse.swt.browser.DefaultType=mozilla -Dorg.eclipse.swt.browser.XULRunnerPath=/path/to/unpacked/xulrunner

That path is the path to the unpacked xulrunner directory.

@berryma4

This comment has been minimized.

Show comment
Hide comment
@berryma4

berryma4 Mar 4, 2014

Member

add this as a fragment?

Member

berryma4 commented Mar 4, 2014

add this as a fragment?

@kasemir

This comment has been minimized.

Show comment
Hide comment
@kasemir

kasemir Mar 4, 2014

Contributor

For the channel access JNI binaries I thought it would make sense to provide them, but that got voted off the island.
For some Linux web library that only few Linux installations might need, even I think it's better left out of the CSS package.

add this as a fragment?

Contributor

kasemir commented Mar 4, 2014

For the channel access JNI binaries I thought it would make sense to provide them, but that got voted off the island.
For some Linux web library that only few Linux installations might need, even I think it's better left out of the CSS package.

add this as a fragment?

@kasemir

This comment has been minimized.

Show comment
Hide comment
@kasemir

kasemir Sep 18, 2014

Contributor

Re-opening it so it's easier to find, because I've had to look for this issue at least time times just so I can email it to people who asked about this.

Doesn't mean we can/should fix it. It's outside of the CSS sources, there is a workaround. Ultimately, I assume this would get fixed in an SWT update.

Contributor

kasemir commented Sep 18, 2014

Re-opening it so it's easier to find, because I've had to look for this issue at least time times just so I can email it to people who asked about this.

Doesn't mean we can/should fix it. It's outside of the CSS sources, there is a workaround. Ultimately, I assume this would get fixed in an SWT update.

@kasemir kasemir reopened this Sep 18, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment