[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich updated JBIDE-9144: ------------------------------------- Description: JUnits for VPE failed to execute on Unubtu 10.4 under Open JDK. Steps to reproduce: 1. Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. 2. New instance of Eclipse will be started. 3. On the "Welcome Screen" click on "Workbench" arrow. 4. Test are about to execute. 5. Eclipse crashes with the message: '# '# A fatal error has been detected by the Java Runtime Environment: '# '# SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 '# '# JRE version: 6.0_20-b20 '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) '# Derivative: IcedTea6 1.9.7 '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 '# Problematic frame: '# C [libsqlite3.so+0x60c1] '# '# An error report file with more information is saved as: '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log '# '# If you would like to submit a bug report, please include '# instructions how to reproduce the bug and visit: '# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ '# 6. Note: when the Welcome screen is active -- texts go fine. Only after it is closed -- fatal error is appeared. 7. Workaround: On "Run Configurations" > Tracing > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After than Welcom Screen will be different, tests won't fail. was: JUnits for VPE failed to execute on Unubtu 10.4 under Open JDK. Steps to reproduce: 1. Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. 2. New instance of Eclipse will be started. 3. On the "Welcome Screen" click on "Workbench" arrow. 4. Test are about to execute. 5. Eclipse crashes with the message: ### A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 JRE version: 6.0_20-b20 Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) Derivative: IcedTea6 1.9.7 Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 Problematic frame: C [libsqlite3.so+0x60c1] An error report file with more information is saved as: /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log If you would like to submit a bug report, please include instructions how to reproduce the bug and visit: https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ ### 6. Note: when the Welcome screen is active -- texts go fine. Only after it is closed -- fatal error is appeared. 7. Workaround: On "Run Configurations" > Tracing > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After than Welcom Screen will be different, tests won't fail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-9144: ------------------------------------------ Fatal error in description happened with XR 1.9.2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-9144: ------------------------------------------ I use Eclipse 3.7 RC3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9144: -------------------------------------------- Does it change if using Helios, Indigo RC4 or even Indigo M6 ? Does it change if you use a Sun JVM instead of open jdk ? Does it change anything if you increase ulimit ? (if its only occurring in RCx's of 3.7 then https://bugs.eclipse.org/bugs/show_bug.cgi?id=349105 might be biting us?) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-9144: ------------------------------------------ JBDS itself works fine on M7 and RC3. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-9144: ------------------------------------ Summary: JUnits for VPE failed to execute (XULRunner 1.9.2/1.9.1 + Eclipse 3.7RC3 + Ubuntu Linux 10.4 x86 32-bit) (was: JUnits for VPE failed to execute (XR 1.9.2/1.9.1 + Eclipse 3.7RC3 )) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-9144: ------------------------------------ Assignee: Denis Maliarevich (was: Vlado Pakan) Description: JUnits for VPE failed to execute on Unubtu 10.4 x86 32-bit under Open JDK and Sun JDK. Steps to reproduce: 1. Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. 2. New instance of Eclipse will be started. 3. On the "Welcome Screen" click on "Workbench" arrow to enter workspace. 4. Tests are about to execute. 5. Eclipse crashes with the message: '# '# A fatal error has been detected by the Java Runtime Environment: '# '# SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 '# '# JRE version: 6.0_20-b20 '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) '# Derivative: IcedTea6 1.9.7 '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 '# Problematic frame: '# C [libsqlite3.so+0x60c1] '# '# An error report file with more information is saved as: '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log '# '# If you would like to submit a bug report, please include '# instructions how to reproduce the bug and visit: '# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ '# 6. Note: when the Welcome screen is active -- texts go fine. Only after it is closed -- fatal error is appeared. 7. Workaround: On "Run Configurations" > "Tracing" > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After that Welcome Screen will be different, tests won't fail. was: JUnits for VPE failed to execute on Unubtu 10.4 under Open JDK. Steps to reproduce: 1. Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. 2. New instance of Eclipse will be started. 3. On the "Welcome Screen" click on "Workbench" arrow to enter workspace. 4. Tests are about to execute. 5. Eclipse crashes with the message: '# '# A fatal error has been detected by the Java Runtime Environment: '# '# SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 '# '# JRE version: 6.0_20-b20 '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) '# Derivative: IcedTea6 1.9.7 '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 '# Problematic frame: '# C [libsqlite3.so+0x60c1] '# '# An error report file with more information is saved as: '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log '# '# If you would like to submit a bug report, please include '# instructions how to reproduce the bug and visit: '# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ '# 6. Note: when the Welcome screen is active -- texts go fine. Only after it is closed -- fatal error is appeared. 7. Workaround: On "Run Configurations" > "Tracing" > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After that Welcome Screen will be different, tests won't fail. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9144: -------------------------------------- Could you attach hs_err_pidXXX.log files? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Jiri Peterka commented on JBIDE-9144: ------------------------------------- Same problem on Fedora 15, 64-bit, JDK 1.6.0_21 What I did: 1. Installed jbds-eap-5.0.0.m2-h657 2. Created Seam war project 3. Opened few pages in VPE 4. Switched to another workspace, after that crash, Log attached # A fatal error has been detected by the Java Runtime Environment: # SIGSEGV (0xb) at pc=0x00007fa5c8b86dd0, pid=13234, tid=140351893849856 # Problematic frame: # C [libsqlite3.so+0x10dd0] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Jiri Peterka commented on JBIDE-9144: ------------------------------------- Replicated twice, actually I had better luck with older JDK 1.6.0_21 than 1.6.0_25 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Jiri Peterka commented on JBIDE-9144: ------------------------------------- Open files limit increase has no effect here. Error is not reliant on specific JDK version (JDK 1.6.0_21,25, OpenJDK) was used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Jiri Peterka commented on JBIDE-9144: ------------------------------------- Pavol tried that on Ubuntu 10.4 32b and wasn't able to reproduce that. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-9144: ------------------------------------------ I also wasn't to reproduce Jiri's crash (he had on Fedora) on my Ubuntu 10.4 32b. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich edited comment on JBIDE-9144 at 6/17/11 8:58 AM: ------------------------------------------------------------------- I also wasn't able to reproduce Jiri's crash (he had on Fedora) on my Ubuntu 10.4 32b on jbdevstudio 5.0.0M2 H673. was (Author: dmaliarevich): I also wasn't able to reproduce Jiri's crash (he had on Fedora) on my Ubuntu 10.4 32b. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich commented on JBIDE-9144: ------------------------------------------ I've switched to XR 1.9.2.17 -- JUnits are still crashing, as before. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Vlado Pakan commented on JBIDE-9144: ------------------------------------ Fedora 14 32bit, Java Sun JDK 1.6.0_25, jbdevstudio-product-linux-gtk-5.0.0.v201106161833N-H677-M2. When running VpeAllTests tests I'm getting this error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7766e0c1, pid=11380, tid=2088758128 # # JRE version: 6.0_25-b06 # Java VM: Java HotSpot(TM) Server VM (20.0-b11 mixed mode linux-x86 ) # Problematic frame: # C [libsqlite3.so+0x60c1] short+0x101 # # An error report file with more information is saved as: # /home/vpakan/ws.jbt/org.jboss.tools.vpe.ui.test/hs_err_pid11380.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Mentioned workaround works. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-9144: ------------------------------------ Summary: VPE crashes with Eclipse 3.7 on some Linux distributions (was: JUnits for VPE failed to execute (XULRunner 1.9.2/1.9.1 + Eclipse 3.7RC3 + Ubuntu Linux 10.4 x86 32-bit)) Description: VPE crashes with Eclipse 3.7 on some Linux distributions: ||OS||XULRunner version||Crashes when unit-testing?||Crashes when using?|| |Ubuntu 10 x86|1.9.1, 1.9.2.16, 1.9.2.17|*YES*|no| |Ubuntu 10 x86_64|1.9.2.16|no|no| |Ubuntu 10 x86_64|1.9.1|???|YES (no problem while we use 1.9.2)| |Fedora 14 x86|1.9.2.16|*YES*|no| |Gentoo x86|1.9.2.16|???|no| *Steps to reproduce JUnit crash:* # Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. # New instance of Eclipse will be started. # On the "Welcome Screen" click on "Workbench" arrow to enter workspace. # Tests are about to execute. # Eclipse crashes with the message: {quote} '# '# A fatal error has been detected by the Java Runtime Environment: '# '# SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 '# '# JRE version: 6.0_20-b20 '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) '# Derivative: IcedTea6 1.9.7 '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 '# Problematic frame: '# C [libsqlite3.so+0x60c1] '# '# An error report file with more information is saved as: '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log '# '# If you would like to submit a bug report, please include '# instructions how to reproduce the bug and visit: '# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ '# {quote} # Note: when the Welcome screen is active -- texts go fine. Only after it is closed -- fatal error is appeared. # Workaround: On "Run Configurations" > "Tracing" > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After that Welcome Screen will be different, tests won't fail. *Steps to reproduce the crash manually:* # Installed jbds-eap-5.0.0.m2-h657 # Created Seam war project # Opened few pages in VPE # Switched to another workspace, after that crash, Log attached {quote} A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x00007fa5c8b86dd0, pid=13234, tid=140351893849856 Problematic frame: C [libsqlite3.so+0x10dd0] {quote} was: JUnits for VPE failed to execute on Unubtu 10.4 x86 32-bit under Open JDK and Sun JDK. Steps to reproduce: 1. Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. 2. New instance of Eclipse will be started. 3. On the "Welcome Screen" click on "Workbench" arrow to enter workspace. 4. Tests are about to execute. 5. Eclipse crashes with the message: '# '# A fatal error has been detected by the Java Runtime Environment: '# '# SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 '# '# JRE version: 6.0_20-b20 '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) '# Derivative: IcedTea6 1.9.7 '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 '# Problematic frame: '# C [libsqlite3.so+0x60c1] '# '# An error report file with more information is saved as: '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log '# '# If you would like to submit a bug report, please include '# instructions how to reproduce the bug and visit: '# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ '# 6. Note: when the Welcome screen is active -- texts go fine. Only after it is closed -- fatal error is appeared. 7. Workaround: On "Run Configurations" > "Tracing" > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After that Welcome Screen will be different, tests won't fail. Summarized problem OSs in the description. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Denis Maliarevich updated JBIDE-9144: ------------------------------------- Description: VPE crashes with Eclipse 3.7 on some Linux distributions: ||OS||XULRunner version||Crashes when unit-testing?||Crashes when using?|| |Ubuntu 10 x86|1.9.1, 1.9.2.16, 1.9.2.17|*YES*|no| |Ubuntu 10 x86_64|1.9.2.16|no|no| |Ubuntu 10 x86_64|1.9.1|???|YES (no problem while we use 1.9.2)| |Fedora 14 x86|1.9.2.16|*YES*|no| |Fedora 15 x86_64|1.9.2.16|???|*YES*| |Gentoo x86|1.9.2.16|???|no| *Steps to reproduce JUnit crash:* # Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. # New instance of Eclipse will be started. # On the "Welcome Screen" click on "Workbench" arrow to enter workspace. # Tests are about to execute. # Eclipse crashes with the message: {quote} '# '# A fatal error has been detected by the Java Runtime Environment: '# '# SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 '# '# JRE version: 6.0_20-b20 '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) '# Derivative: IcedTea6 1.9.7 '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 '# Problematic frame: '# C [libsqlite3.so+0x60c1] '# '# An error report file with more information is saved as: '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log '# '# If you would like to submit a bug report, please include '# instructions how to reproduce the bug and visit: '# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ '# {quote} # Note: when the Welcome screen is active -- JUnit tests go fine. Only after it is closed -- fatal error is appeared. # Workaround: On "Run Configurations" > "Tracing" > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After that Welcome Screen will be different, tests won't fail. *Steps to reproduce the crash manually:* # Installed jbds-eap-5.0.0.m2-h657 # Created Seam war project # Opened few pages in VPE # Switched to another workspace, after that crash, Log attached {quote} A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x00007fa5c8b86dd0, pid=13234, tid=140351893849856 Problematic frame: C [libsqlite3.so+0x10dd0] {quote} was: VPE crashes with Eclipse 3.7 on some Linux distributions: ||OS||XULRunner version||Crashes when unit-testing?||Crashes when using?|| |Ubuntu 10 x86|1.9.1, 1.9.2.16, 1.9.2.17|*YES*|no| |Ubuntu 10 x86_64|1.9.2.16|no|no| |Ubuntu 10 x86_64|1.9.1|???|YES (no problem while we use 1.9.2)| |Fedora 14 x86|1.9.2.16|*YES*|no| |Fedora 15 x86_64|1.9.2.16|???|*YES*| |Gentoo x86|1.9.2.16|???|no| *Steps to reproduce JUnit crash:* # Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin. # New instance of Eclipse will be started. # On the "Welcome Screen" click on "Workbench" arrow to enter workspace. # Tests are about to execute. # Eclipse crashes with the message: {quote} '# '# A fatal error has been detected by the Java Runtime Environment: '# '# SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624 '# '# JRE version: 6.0_20-b20 '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 ) '# Derivative: IcedTea6 1.9.7 '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1 '# Problematic frame: '# C [libsqlite3.so+0x60c1] '# '# An error report file with more information is saved as: '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log '# '# If you would like to submit a bug report, please include '# instructions how to reproduce the bug and visit: '# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ '# {quote} # Note: when the Welcome screen is active -- texts go fine. Only after it is closed -- fatal error is appeared. # Workaround: On "Run Configurations" > "Tracing" > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After that Welcome Screen will be different, tests won't fail. *Steps to reproduce the crash manually:* # Installed jbds-eap-5.0.0.m2-h657 # Created Seam war project # Opened few pages in VPE # Switched to another workspace, after that crash, Log attached {quote} A fatal error has been detected by the Java Runtime Environment: SIGSEGV (0xb) at pc=0x00007fa5c8b86dd0, pid=13234, tid=140351893849856 Problematic frame: C [libsqlite3.so+0x10dd0] {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9144: -------------------------------------- Eclipse 3.7 crashes when running VPE tests (or when using XULRunner 1.9.x) because Eclipse 3.7 uses WebKit as the Browser's underlying renderer (see http://www.eclipse.org/swt/faq.php#howusewebkit). As for Eclipse 3.7 Linux GTK, WebKit is always used when a browser is created with SWT.NONE (or SWT.WEBKIT). It is used in the Javadoc view, Declaration view, in the Welcome page, etc. The only way to avoid using WebKit is to remove or invalidate it. The problem happens because XULRunner and WebKit use incompatible versions of the sqlite3 libraries. The problem can occur on some Linux distribution (32bit and 64bit) and doesn't depend on the XULRunner version. If a Linux distribution contains WebKit with an incompatible sqlite, Eclipse will crash. This can be tested in the following way: - start VPE tests on a machine on which this bug can be reproduced (FC15 64bit or Ubuntu 11.04 32bit with XULRunner 1.9.2.16, for instance) Ensure that Eclipse crashes when running the VPE tests. To make sure that WebKit is a problem, do the following: - move /usr/lib64/libsqlite3* libraries to a directory which isn't on the LD_LIBRARY_PATH (your home directory, for instance). If you are reproducing the bug on a 32bit machine, the sqlite libraries will probably be in the /usr/lib directory. You can also remove the WebKit package. WebKit renderer won't be started and the tests will be executed correctly. The SWT team knows about this issue and they created a fix for it (see the comment in the BrowserFactory.createWebBrowser method). However, the fix doesn't work in Eclipse >=RC3. It is possible to fix Eclipse 3.7RC4 by loading additional XULRunner libraries, but that fix wouldn't work in Eclipse 3.7 I20110613-1736. I think it isn't possible that WebKit and XULRunner 1.9.x work simultaneously unless the system's WebKit and system's XULRunner are used. The issue can't be solved by compiling XULRunner with the system's sqlite because that wouldn't work on different Linux distributions. The best solution is to ask the SWT team to add a variable (org.eclipse.swt.browser.UseWebKitGTK, for instance; this variable exists in Eclipse 3.6.2). If the variable is set to false, Eclipse wouldn't try to use WebKit (at least when using SWT.NONE). It would also be necessary to load the org.eclipse.swt.browser.WebKitInitializer or some similar class that could set this variable before showing up the Welcome page. The user should be able to decide whether to use WebKit or not. Attached are patches against SWT and org.jboss.tools.xulrunner.initializer. We can remove the swt-webkit libraries from the swt fragment using Eclipse Transforms. However, this would work in JBDS only. We can also advice the users that want to use the VPE editor to remove/move temporary the WebKit package or the system's sqlite libraries. I have also created patched org.eclipse.swt.gtk.x86_64/org.eclipse.swt.gtk.linux.x86 plugin. If you replace this plugin with the corresponding plugin from your distribution, apply the o.j.t.xulrunner patch, you won't be able to reproduce the Eclipse crash. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9144: ----------------------------------- Issue 1: SWT patched plugins: Working on getting this into the JBT Indigo Reqs site. http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosst... http://download.jboss.org/jbosstools/updates/requirements/swt/build.xml (PDE p2 publisher script) Currently, if you build the site metadata w/ the build.xml script, then try to install from it, I get an error about org.eclipse.swt.gtk.linux.x86_64 0.0.0 not being resolved. (I'm on 32-bit linux here.) --- Issue #2: XR.initializer patch: Can this be applied in trunk / M2 branch, or does it need to also appear on a patch site? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9144: -------------------------------------- I have committed the changed patch so that now the user can enable WebKit. If the user doesn't add any property, XULRunner will be loaded and WebKit disabled (if the patched swt plugins are included). The user can disable XULRunner and enable WebKit by adding the following properties: -Dorg.jboss.tools.vpe.loadxulrunner=false -Dorg.eclipse.swt.browser.UseWebKitGTK=true The org.eclipse.swt.browser.UseWebKitGTK property is available on Linux GTK only. I have also configured o.j.t.xulrunner.initializer as a singleton. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9144: -------------------------------------------- as far as I can see from source tab code was only committed to trunk. Is anything needed in the 3.3.0.M2 branch ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-9144: ----------------------------------- changes to http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosst... need not be ported to branch - only trunk is current w.r.t. the contents on http://download.jboss.org/jbosstools/ However, what I posted there is incomplete - didn't get a chance to build the site and resolve he missing / broken metadata. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9144?page=com.atlassian.jira.plugin... ] Snjezana Peco commented on JBIDE-9144: -------------------------------------- The org.jboss.tools.xulrunner.initializer.patch2 patch has been committed to the 3.3.0.M2 branch too. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira