java crashed with SIGSEGV

Bug #861063 reported by Jared
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openjdk-6 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Opening Vuze and trying to view a subscription freezes or crashes Vuze and results in this bug. Additionally every time Vuze crashes, Libre Office launches spontaneously.

 I am using 11.10 b2 development build. I have all the latest updates as of 9:20PM EDT on 09/27/2011

Installed: 4.18.0-0ubuntu1
  Candidate: 4.18.0-0ubuntu1
  Version table:

openjdk-6-jre 6b23~pre10-0ubuntu3

openjdk-6-jre-headless 6b23~pre10-0ubuntu3

default-jre-headless 1:1.6-42ubuntu2

libreoffice1:3.4.3-1ubuntu3

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: openjdk-6-jre-headless 6b23~pre10-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Sep 27 21:07:32 2011
Disassembly: => 0xb48698dd: Cannot access memory at address 0xb48698dd
ExecutablePath: /usr/lib/jvm/java-6-openjdk/jre/bin/java
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
LocalLibraries: /home/jaredvanvolkenburg/.swt/lib/linux/x86/libswt-pi-gtk-3802.so /home/jaredvanvolkenburg/.swt/lib/linux/x86/libswt-xpcominit-gtk-3802.so /opt/google/talkplugin/lib/libCg.so /home/jaredvanvolkenburg/.swt/lib/linux/x86/libswt-atk-gtk-3802.so /home/jaredvanvolkenburg/.swt/lib/linux/x86/libswt-cairo-gtk-3802.so /opt/google/picasa/3.0/lib/npPicasa3.so /opt/google/talkplugin/libnpgoogletalk.so /home/jaredvanvolkenburg/.swt/lib/linux/x86/libswt-gtk-3802.so /opt/google/talkplugin/libnpgtpo3dautoplugin.so /opt/google/talkplugin/lib/libCgGL.so /home/jaredvanvolkenburg/.swt/lib/linux/x86/libswt-webkit-gtk-3802.so
ProcCmdline: java -Xmx128m -cp ./Azureus2.jar:./swt.jar -Djava.library.path=/home/username/Vuze/vuze -Dazureus.install.path=/home/username/Vuze/vuze -Dazureus.script=/home/username/Vuze/vuze/vuze -Dazureus.script.version=2 org.gudy.azureus2.ui.swt.Main
SegvAnalysis:
 Segfault happened at: 0xb48698dd: Cannot access memory at address 0xb48698dd
 PC (0xb48698dd) ok
 Stack memory exhausted (SP below stack segment)
 SP (0xa3718c2c) ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: openjdk-6
Stacktrace:
 #0 0xb48698dd in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xa3718c2c
StacktraceTop: ?? ()
Title: java crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-12 (15 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare video

Revision history for this message
Jared (jared-vanvolkenburg) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb48698dd in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xa3718c2c
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in openjdk-6 (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

outdated debug symbol package for libk5crypto3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libavahi-common3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for libgpg-error0: package version 1.10-0.3ubuntu1 dbgsym version 1.10-0.2ubuntu1
outdated debug symbol package for libkrb5support0: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libkrb5-3: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libgssapi-krb5-2: package version 1.9.1+dfsg-1ubuntu1 dbgsym version 1.8.3+dfsg-5ubuntu2.1
outdated debug symbol package for libavahi-client3: package version 0.6.30-4ubuntu1 dbgsym version 0.6.30-0ubuntu2
outdated debug symbol package for dpkg: package version 1.16.0.3ubuntu3 dbgsym version 1.16.0~ubuntu7.1
outdated debug symbol package for libltdl7: package version 2.4-2ubuntu1 dbgsym version 2.2.6b-2ubuntu3
outdated debug symbol package for libxslt1.1: package version 1.1.26-7 dbgsym version 1.1.26-6build1
outdated debug symbol package for libgdk-pixbuf2.0-0: package version 2.24.0-1ubuntu1 dbgsym version 2.24.0-1
outdated debug symbol package for gtk2-engines-pixbuf: package version 2.24.6-0ubuntu3 dbgsym version 2.24.4-0ubuntu2
outdated debug symbol package for libgstreamer-plugins-base0.10-0: package version 0.10.35-1 dbgsym version 0.10.32-1ubuntu5
outdated debug symbol package for libtotem-plparser17: package version 2.32.5-2 dbgsym version 2.32.4-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Revision history for this message
Jared (jared-vanvolkenburg) wrote :

I looked at the list of files that Apport listed as being outdated. I verified that the files I have installed on my system are the versions that are installed by default on the current version of oneiric 11.10 b2 with the latest installs as of 9/27/2011 10:30PM EDT.

The versions required by the current version of Apport Retracing Service are not available on oneiric; resulting in Java bugs not being able to be reported and processed correctly.

Changed in openjdk-6 (Ubuntu):
status: Invalid → Incomplete
status: Incomplete → New
tags: added: apport-retracing-service java
Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and is no more supported

Changed in openjdk-6 (Ubuntu):
status: New → Invalid
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.