Announcement Announcement Module
Collapse
No announcement yet.
STS 3.2.0 release crashing on Fedora 19 and JDK Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • STS 3.2.0 release crashing on Fedora 19 and JDK

    Hello,

    I have a new installation of Fedora 19 and STS 3.2.0. STS keeps crashing very often, so it is practicaly unusable ... It states that JDK has a problem and then it crashes ... I also tried to use Sun's java and still got the same bug ...

    Environment:
    Code:
    [mr@localhost ~]$ uname -a
    Linux localhost.localdomain 3.9.9-301.fc19.x86_64 #1 SMP Thu Jul 4 15:10:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
    [m@localhost ~]$ java -version
    java version "1.7.0_25"
    OpenJDK Runtime Environment (fedora-2.3.10.4.fc19-x86_64)
    OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
    [m@localhost ~]$ javac -version
    javac 1.7.0_25
    System log:
    Code:
    Jul  8 08:19:17 localhost gnome-session[1273]: Entering running state
    Jul  8 08:19:17 localhost /etc/gdm/Xsession[1273]: JS LOG: GNOME Shell started at Mon Jul 08 2013 08:19:17 GMT+0200 (CEST)
    Jul  8 08:19:17 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: Log level 16: STACK_OP_ADD: window 0x1a00001 already in stack
    Jul  8 08:19:17 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: Log level 16: STACK_OP_ADD: window 0x1a00001 already in stack
    Jul  8 08:19:17 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: CurrentTime used to choose focus window; focus window may not be correct.
    Jul  8 08:19:17 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
    Jul  8 08:19:22 localhost /etc/gdm/Xsession[1273]: (tracker-miner-fs:1511): GLib-CRITICAL **: g_timer_continue: assertion `timer->active == FALSE' failed
    Jul  8 08:19:23 localhost /etc/gdm/Xsession[1273]: (process:1634): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
    Jul  8 08:19:29 localhost systemd-logind[522]: Removed session c1.
    Jul  8 08:19:49 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400003 (Spring Too)
    Jul  8 08:19:49 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
    Jul  8 08:20:13 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400209 (Spring - D)
    Jul  8 08:20:13 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
    Jul  8 08:20:16 localhost chronyd[531]: Selected source 194.249.198.30
    Jul  8 08:20:27 localhost /etc/gdm/Xsession[1273]: [debug] execute contextualize
    Jul  8 08:20:27 localhost /etc/gdm/Xsession[1273]: [debug] execute contextualize
    Jul  8 08:20:29 localhost /etc/gdm/Xsession[1273]: [debug] execute contextualize
    Jul  8 08:20:29 localhost /etc/gdm/Xsession[1273]: [debug] execute contextualize
    Jul  8 08:20:32 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2403968 (Run As )
    Jul  8 08:20:32 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
    Jul  8 08:20:35 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400209 (Spring - D)
    Jul  8 08:20:35 localhost /etc/gdm/Xsession[1273]: Opozorilo upravljalnika oken: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # A fatal error has been detected by the Java Runtime Environment:
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #  SIGSEGV (0xb) at pc=0x000000312326d9b1, pid=1718, tid=139803948132096
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # JRE version: 7.0_25-b15
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode linux-amd64 compressed oops)
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # Problematic frame:
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # C  [libsoup-2.4.so.1+0x6d9b1]  soup_session_feature_detach+0x11
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # An error report file with more information is saved as:
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # /home/messner/hs_err_pid1718.log
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # If you would like to submit a bug report, please visit:
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #   http://bugreport.sun.com/bugreport/crash.jsp
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # The crash happened outside the Java Virtual Machine in native code.
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: # See problematic frame for where to report the bug.
    Jul  8 08:20:46 localhost /etc/gdm/Xsession[1273]: #
    Jul  8 08:20:56 localhost abrtd: Directory 'ccpp-2013-07-08-08:20:46-1718' creation detected
    Jul  8 08:20:56 localhost abrt[1887]: Saved core dump of pid 1718 (/usr/java/jdk1.7.0_25/jre/bin/java) to /var/tmp/abrt/ccpp-2013-07-08-08:20:46-1718 (836427776 bytes)
    Jul  8 08:20:56 localhost abrtd: Size of '/var/tmp/abrt' >= 1000 MB, deleting 'ccpp-2013-07-08-08:08:19-1939'
    Jul  8 08:20:58 localhost abrtd: Generating core_backtrace
    Jul  8 08:20:58 localhost abrtd: Generating backtrace
    Jul  8 08:21:00 localhost abrtd: Backtrace is generated, 86623 bytes
    Jul  8 08:21:00 localhost abrtd: Unable to open '/home/messner/bin/springsource/sts-3.2.0.RELEASE/configuration/org.eclipse.osgi/bundles/685/1/.cp/libswt-webkit-gtk-3836.so': Permission denied
    Jul  8 08:21:00 localhost abrtd: Core backtrace is generated and saved, 1125 bytes
    Jul  8 08:21:03 localhost abrtd: New problem directory /var/tmp/abrt/ccpp-2013-07-08-08:20:46-1718, processing
    Jul  8 08:21:06 localhost dbus-daemon[524]: dbus[524]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
    Jul  8 08:21:06 localhost dbus[524]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service'
    Jul  8 08:21:06 localhost systemd[1]: Starting Fingerprint Authentication Daemon...
    Jul  8 08:21:06 localhost dbus-daemon[524]: dbus[524]: [system] Successfully activated service 'net.reactivated.Fprint'
    Jul  8 08:21:06 localhost dbus[524]: [system] Successfully activated service 'net.reactivated.Fprint'
    Jul  8 08:21:06 localhost fprintd[1975]: Launching FprintObject
    Jul  8 08:21:06 localhost systemd[1]: Started Fingerprint Authentication Daemon.
    Jul  8 08:21:06 localhost fprintd[1975]: ** Message: D-Bus service launched with name: net.reactivated.Fprint
    Jul  8 08:21:06 localhost fprintd[1975]: ** Message: entering main loop
    Any ideas ?
    Last edited by messner; Jul 8th, 2013, 02:42 AM.

  • #2
    Hey!

    This looks like this bug at Eclipse:
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=405786

    Can you try the workaround that is described there? (adding -Dorg.eclipse.swt.browser.DefaultType=mozilla to sts.ini).

    HTH,
    Martin

    Comment


    • #3
      Closed

      Originally posted by Martin Lippert View Post
      Can you try the workaround that is described there? (adding -Dorg.eclipse.swt.browser.DefaultType=mozilla to sts.ini).
      Thank you ... it works now ))

      Problem solved ...

      Comment


      • #4
        Glad to hear the workaround works. And thanks for letting us know!

        Cheers,
        -Martin

        Comment

        Working...
        X