openjdk-7 crashed while running vuze

Bug #1242029 reported by kleber
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
openjdk-7 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f954f566528, pid=3894, tid=140279267034880
#
# 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 [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18
#
# 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/kleber/vuze/hs_err_pid3894.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-7/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
./azureus: linha 204: 3894 Abortado (imagem do núcleo gravada) ${JAVA_PROGRAM_DIR}java "${JAVA_ARGS}" -cp "${CLASSPATH}" -Djava.library.path="${PROGRAM_DIR}" -Dazureus.install.path="${PROGRAM_DIR}" -Dazureus.script="$0" $JAVA_PROPS $START_CLASS "$@"
Exit from Azureus complete
No shutdown tasks to do
Azureus TERMINATED.

Revision history for this message
kleber (klebermo) wrote :
Revision history for this message
JJ (bjustjones) wrote :

I get a very similar crash ( libgobject-2.0.so )when using a brand new Eclipse ADT bundle from Android on a fairly new install of Kubuntu and opening any other directory than the default "~/workspace".
I might get it to start with workspace in ~/cordova but then it will crash when importing a project anyways.
Mine is a 32 bit installation.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openjdk-7 (Ubuntu):
status: New → Confirmed
JJ (bjustjones)
Changed in openjdk-7 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
JJ (bjustjones) wrote :

If reproduceable this would be a problem with libswt-cairo-gtk or libswt-[gnome/webkit/mozilla]-gtk libraries.

As for Eclipse I avoided the problem by using a newer version of Eclipse than the one that Android is packaging with their ADT bundle. Not related to Ubuntu at all.

 I put the status to incomplete until someone else confirms the issue with Vuze.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for openjdk-7 (Ubuntu) because there has been no activity for 60 days.]

Changed in openjdk-7 (Ubuntu):
status: Incomplete → Expired
Changed in openjdk-7 (Ubuntu):
status: Expired → Confirmed
Revision history for this message
pazuzuthewise (pazuzuthewise) wrote :

pazuzu@pazuzu-AO756:~ > azureus
file:/usr/lib/jni/ ; file:/usr/lib/java/ ; file:/usr/share/java/Azureus2.jar ; file:/usr/share/java/log4j-1.2-1.2.17.jar ; file:/usr/share/java/commons-cli-1.2.jar ; file:/usr/lib/java/swt-gtk-3.8.2.jar ; file:/home/pazuzu/
changeLocale: *Default Language* != English (United States). Searching without country..
changeLocale: Searching for language English in *any* country..
changeLocale: no message properties for Locale 'English (United States)' (en_US), using 'English (default)'
UIFunctions/ImageLoad took 0ms
new shell took 202ms
new shell setup took 133ms
skin init took 251ms
MainMenu init took 326ms
pre skin widgets init took 25ms
skin widgets (1/2) init took 276ms
skin widgets (2/2) init took 206ms
pre SWTInstance init took 0ms
Init Core Columns took 178ms
SWTInstance init took 31ms
shell.layout took 0ms
---------SHOWN AT 1395020932039;3545ms
---------DONE DISPATCH AT 1395020932705;4186ms
---------READY AT 1395020932730;4211ms
shell.open took 691ms
processStartupDMS took 0ms
postPluginSetup init took 0ms
Locale Initializing took 25ms
Core Initializing took 1230ms
psDMS 7ms

(Vuze:6438): GLib-GObject-CRITICAL **: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed

(Vuze:6438): GLib-GObject-CRITICAL **: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed

(Vuze:6438): GLib-GObject-CRITICAL **: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed

(Vuze:6438): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x6b271bfe, pid=6438, tid=1802115904
#
# JRE version: OpenJDK Runtime Environment (7.0_51) (build 1.7.0_51-b00)
# Java VM: OpenJDK Server VM (24.45-b08 mixed mode linux-x86 )
# Problematic frame:
# C [libgobject-2.0.so.0+0x16bfe] g_object_get_qdata+0x1e
#
# 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/pazuzu/hs_err_pid6438.log
#
# If you would like to submit a bug report, please include
# instructions on how to reproduce the bug and visit:
# http://icedtea.classpath.org/bugzilla
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted
[134]pazuzu@pazuzu-AO756:~ >

Revision history for this message
pazuzuthewise (pazuzuthewise) wrote :
Revision history for this message
pazuzuthewise (pazuzuthewise) wrote :

It happens both with the vuze package 5.3.0.0-1~getdeb1 and with 4.3.0.6-5 from the official saucy repo.

Revision history for this message
Sergio Callegari (callegar) wrote :

Apparently also the areca backup program crashes very similarly.

I am experiencing this with kubuntu 64 bit saucy and trusty.

To reproduce:

- install areca 64bit from http://sourceforge.net/projects/areca/files/areca-stable/
- start areca
- right click on workspace pane (top left pane) and select new target (or do CTRL+T)
- Press cancel

You get

1) tons of SWT critical errors

GLib-GObject-CRITICAL **: g_closure_add_invalidate_notifier: assertion 'closure->n_inotifiers < CLOSURE_MAX_N_INOTIFIERS' failed

2) a couple of warnings

GLib-GObject-WARNING **: /build/buildd/glib2.0-2.38.1/./gobject/gclosure.c:697: unable to remove uninstalled invalidation notifier: 0x7f6f4de0fbe0 (0x7f6f54996930)

3) a final segfault at
C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18

If it is the same bug, note that this seems to be SWT related, and not related to openjdk-7 since it happens also with java 6.

I wonder if it can be https://bugs.eclipse.org/bugs/show_bug.cgi?id=407077

Revision history for this message
Sergio Callegari (callegar) wrote :

A couple of integrations to my previous comment.

1) Areca includes an swt.jar file with its own libswt-gtk. This version of swt-gtk conflicts with the glib in saucy and trusty 64 bit and makes areca crash.

2) In order to make areca work with ubuntu's libswt-gtk it is sufficient to get areca's swt.jar out of the way. For instance:

mv <areca dir>/lib/swt.jar <areca dir>/lib/swt.jar.bak

Unfortunately, this does not help. Areca segfaults even with the ubuntu's libswt-gtk that also seems to have issues with recent glib.

3) Installing in the areca lib directory the latest swt.jar downloaded from eclipse which brings in libswt-gtk-4332.so (and uninstalling ubuntu's libswt) the issue is fixed.

IMHO, this indicates that there is an issue in swt.jar that has been fixed in the latest swt. Maybe, the fix is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=407077.

In any case, I believe that the libswt that is in trusty should be fixed or updated.

Revision history for this message
olin@atkinsontech.com (olin-atkinsontech) wrote :

I have a core dump from a crash in

Problematic frame:
# C [libgobject-2.0.so.0+0x19528] g_object_get_qdata+0x18

If anyone thinks it will help.

Revision history for this message
olin@atkinsontech.com (olin-atkinsontech) wrote :

By the way, that is for the original issue, vuze crashing. Also, I don't know if it matters but I am currently running

Linux atkinson-phenomIIx4 3.13.11-03131103-generic #201406131635 SMP Fri Jun 13 20:36:17 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I can go back to the standard if it matters.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.