[jbosstools-issues] [JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

Alexander Kurtakov (JIRA) issues at jboss.org
Thu Jun 16 12:37:00 EDT 2016


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

Alexander Kurtakov commented on JBDS-3953:
------------------------------------------

Would you please also try:
export SWT_WEBKIT2=1
./jbdevstudio

By doing so webkitgtk4 will be used where plugins are run out of process and thus if a plugin crashes it will not take down the main process with it. There were many such cases in the past caused by Google Talk, Bluejeans and etc. While this is not a fix itself it would at least tell us whether we face yet another browser plugin issue.


> JBoss Studio Developer crash at startup on Fedora 24
> ----------------------------------------------------
>
>                 Key: JBDS-3953
>                 URL: https://issues.jboss.org/browse/JBDS-3953
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: upstream
>    Affects Versions: 9.1.0.GA
>         Environment: Fedora 24 
> openjdk full version "1.8.0_92-b14"
>            Reporter: Donato Marrazzo
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 10.x
>
>         Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip
>
>
> After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash.
> Despite the console message, no core dump is generated.
> This is the cmd line output:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml]
> openjdk version "1.8.0_92"
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)
> 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml]
> 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml]
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14)
> # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C  [libjavascriptcoregtk-3.0.so.0+0x4d4bfe]  JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e
> #
> # Core dump written. Default location: /home/donato/core or core.12689
> #
> # An error report file with more information is saved as:
> # /home/donato/hs_err_pid12689.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.
> #



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list