[jbosstools-issues] [JBoss JIRA] (JBIDE-18979) Unable to run CordovaSim with Fedora 21 KDE

Ilya Buziuk (JIRA) issues at jboss.org
Mon Jan 5 13:07:29 EST 2015


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

Ilya Buziuk commented on JBIDE-18979:
-------------------------------------

[~vpakan] that's weird cause I'm not able to reproduce this on my machine :-(
The only problem I have is (1) from my previous comment. Here is my fedora info !fedora.png|thumbnail!
Could you possibly try to reproduce this issue on another machine? is  libwebkitgtk was installed correctly - http://tools.jboss.org/documentation/faq/browsersim.html#platform-specific-questions ? 

> Unable to run CordovaSim with Fedora 21 KDE
> -------------------------------------------
>
>                 Key: JBIDE-18979
>                 URL: https://issues.jboss.org/browse/JBIDE-18979
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: browsersim, cordovasim
>    Affects Versions: 4.2.1.Final
>         Environment: JBDS 8.0.1.CR1-v20141207-0100-B352, Java Oracle 1.8
> Fedora 21 KDE 64 bit
>            Reporter: Vlado Pakan
>            Assignee: Ilya Buziuk
>            Priority: Critical
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: fedora.png, webkit.png
>
>
> 1. Run default Hybrid Mobile app with CordovaSim
> {noformat}
> No bp log location saved, using default.
> [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB
> [000:000] Computer model: Not available
> [000:000] Browser XEmbed support present: 1
> [000:000] Browser toolkit is Gtk2.
> [000:003] Using Gtk2 toolkit
> No bp log location saved, using default.
> [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB
> [000:001] Computer model: Not available
> [000:497] Warning(optionsfile.cc:30): Load: Could not open file, err=2
> [000:497] No bp log location saved, using default.
> [000:497] Cpu: 6.42.7, x4, 3500Mhz, 7867MB
> [000:497] Computer model: Not available
> [000:498] Browser XEmbed support present: 1
> [000:498] Browser toolkit is Gtk2.
> [000:498] Using Gtk2 toolkit
> [000:003] Warning(optionsfile.cc:30): Load: Could not open file, err=2
> [000:003] No bp log location saved, using default.
> [000:004] Cpu: 6.42.7, x4, 3500Mhz, 7867MB
> [000:004] Computer model: Not available
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x000000370a80c42b, pid=13580, tid=140558422947584
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C  [ld-linux-x86-64.so.2+0xc42b]
> #
> # 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/vpakan/hs_err_pid13580.log
> #
> # 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.
> #
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)


More information about the jbosstools-issues mailing list