[
https://issues.jboss.org/browse/JBIDE-21589?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-21589 at 1/28/16 3:35 PM:
-------------------------------------------------------------------
[~mlabuda]I cant reproduce this but this very much looks like the webkit problem there is
in GTK3, which crashes Eclipse. I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @
0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
It can be reproduced if you open the internal browser, open the javadoc view or code
autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have google talk or bluejeans plugin installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please?
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
was (Author: adietish):
[~mlabuda]I cant reproduce this but this very much looks like the webkit problem there is
in GTK3, which crashes Eclipse. I see the following in the stack:
{code}
J 26556 C1 org.eclipse.swt.browser.WebKit.webkit_notify_progress(JJ)J (118 bytes) @
0x00007f0dd1118bc4 [0x00007f0dd1118320+0x8a4]
{code}
It can be reproduced if you open the internal browser, open the javadoc view or code
autocompletion (and other cases I am not aware of).
It happens in GTK3 system which have google talk or bluejeans plugin installed.
It should not happen any more if you either:
* disable GTK3: export SWT_GTK3=0 in console before launching Eclipse
* switch the internal browser to firefox
* add -Dorg.eclipse.swt.browser.DefaultType=mozilla to your eclipse.ini
* ...
Can try this, please?
The Eclipse bugzillas are here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=334466
JBDS crash sometimes when opening Show in Console on a project
--------------------------------------------------------------
Key: JBIDE-21589
URL:
https://issues.jboss.org/browse/JBIDE-21589
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Environment: Fedora 22
openjdk 8.0_71-b15
Reporter: Marián Labuda
Priority: Critical
Labels: openshift_v3
Attachments: log.txt
Crash log
{code}
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f0cfe0bbcaf, pid=13526, tid=139697620236032
#
# JRE version: OpenJDK Runtime Environment (8.0_71-b15) (build 1.8.0_71-b15)
# Java VM: OpenJDK 64-Bit Server VM (25.71-b15 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libwebkitgtk-3.0.so.0+0x47bcaf]
#
# 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/mlabuda/testing/jbds/910Beta2stable/hs_err_pid13526.log
#
# If you would like to submit a bug report, please visit:
#
http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
{code}
For more thread dump see attached log.txt
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)