[jbosstools-issues] [JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench

Nick Boldt (JIRA) issues at jboss.org
Wed Dec 18 11:43:33 EST 2013


    [ https://issues.jboss.org/browse/JBIDE-16280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932416#comment-12932416 ] 

Nick Boldt edited comment on JBIDE-16280 at 12/18/13 11:43 AM:
---------------------------------------------------------------

One idea:

https://github.com/jbosstools/jbosstools-xulrunner/pull/12
https://github.com/jbosstools/jbosstools-build-sites/pull/125

Will likely have to remove things from VPE too, such as:

https://github.com/jbosstools/jbosstools-vpe/blob/master/features/org.jboss.tools.xulrunner.feature/feature.xml#L36-L52
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jboss.tools.vpe.xulrunner/META-INF/MANIFEST.MF
https://github.com/jbosstools/jbosstools-vpe/blob/master/tests/pom.xml

plus, for swt/xulrunner these files may also be affected:

https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86_64.java
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86.java
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/WebKitBrowserFactory.java
https://github.com/jbosstools/jbosstools-vpe/blob/master/plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser.java
https://github.com/jbosstools/jbosstools-vpe/blob/master/products/browsersim-standalone/pom.xml

---

When I built locally the Xulrunner site from master branch after applying the first PR, the plugins were missing from the site. Then I built the JBT aggregate site from master branch using the second PR above, but both lin_32 and lin_64 plugins were present in the resulting site (presumably pulled in from org.jboss.tools.xulrunner.feature and org.jboss.tools.vpe.xulrunner depending on them).

But when I installed the VPE feature (org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131213-1617-B466.jar) into Eclipse 4.4.0.M3 Luna JEE bundle, it was OK - Eclipse didn't freeze or crash. 

It wasn't until I then installed all the rest of JBT (including org.jboss.tools.vpe.browsersim.browser) that the crashing/halting behaviour came back (actually I'm running w/ export GTK3=0, and it means it takes forever for Eclipse to start, but when it does, it works). 

So this test is inconclusive. Will have to rip more stuff out of VPE to do a more complete test, and disable the GTK3=0 workaround.


                
      was (Author: nickboldt):
    One idea:

https://github.com/jbosstools/jbosstools-xulrunner/pull/12
https://github.com/jbosstools/jbosstools-build-sites/pull/125

Will likely have to remove things from VPE too, such as:

https://github.com/jbosstools/jbosstools-vpe/blob/master/features/org.jboss.tools.xulrunner.feature/feature.xml#L36-L52

plus:

./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86_64.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/internal/WebKitBrowser_gtk_linux_x86.java
./plugins/org.jboss.tools.vpe.browsersim.browser/src/org/jboss/tools/vpe/browsersim/browser/WebKitBrowserFactory.java

and

./plugins/org.jboss.tools.vpe.xulrunner/META-INF/MANIFEST.MF
./plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/browser/XulRunnerBrowser.java
./products/browsersim-standalone/pom.xml
./tests/pom.xml

---

When I built locally the Xulrunner site from master branch after applying the first PR, the plugins were missing from the site. Then I built the JBT aggregate site from master branch using the second PR above, but both lin_32 and lin_64 plugins were present in the resulting site (presumably pulled in from org.jboss.tools.xulrunner.feature and org.jboss.tools.vpe.xulrunner depending on them).

But when I installed the VPE feature (org.jboss.tools.vpe.xulrunner_3.5.100.Alpha1-v20131213-1617-B466.jar) into Eclipse 4.4.0.M3 Luna JEE bundle, it was OK - Eclipse didn't freeze or crash. 

It wasn't until I then installed all the rest of JBT (including org.jboss.tools.vpe.browsersim.browser) that the crashing/halting behaviour came back (actually I'm running w/ export GTK3=0, and it means it takes forever for Eclipse to start, but when it does, it works). 

So this test is inconclusive. Will have to rip more stuff out of VPE to do a more complete test, and disable the GTK3=0 workaround.


                  
> VPE/XulRunner crashes workbench
> -------------------------------
>
>                 Key: JBIDE-16280
>                 URL: https://issues.jboss.org/browse/JBIDE-16280
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: xulrunner
>    Affects Versions: 4.2.0.Alpha1
>            Reporter: Mickael Istria
>            Priority: Critical
>             Fix For: 4.2.0.Alpha2
>
>         Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C  [libxul.so+0xc81255]  JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list