Azureus crashes with SIGSEGV

Bug #71220 reported by Dodo Guy on 2006-11-10
2
Affects Status Importance Assigned to Milestone
azureus (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: azureus

Azureus crashes when used with sun-java5-jre. It seems to work ok when used with gcj-4.1-base.

The vanilla package from azureus.sourceforge.net works fine with sun-java5-jre.

I will attach the output of reportbug and the crash log.

Attached the Bug report as generated by reportbug.

This was originally reported for the azureus package. Now I'd rather assume that it's related to sun-java5-jre since the problem does not occur with the gcj vm.

Here is the error message, the VM error logfile hs_err_pid6363.log is attached:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb052ed02, pid=6363, tid=3084555952
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_08-b03 mixed mode, sharing)
# Problematic frame:
# C [libglibjni-0.4.so+0x8d02]
#
# An error report file with more information is saved as hs_err_pid6363.log
#

I have just downloaded http://prdownloads.sourceforge.net/azureus/Azureus_2.5.0.0_linux.tar.bz2?download and installed it in /opt and it works without problems with sun-java5-jre. (all gcj packages removed)

description: updated
Simon Ruggier (simon80) wrote :

I seem to have the same issue.

alex f (acid-punk) wrote :

I have these crashes as well. The error report always differs a little bit. I found that the reason why azureus keeps crashing, seems to be the log files in ~/.azureus/logs/ when I delete those azureus starts up again without crashing right again.

For example azureus logs in logs/alerts_1.log that I'm having NAT issues and it needs an open UDP port etc.

I'm not sure if switching from sun-jdk to gcj makes azureus not choke on these log files.

Bug #68020 might be a duplicate?

It seems highly unlikely to me that Azureus would crash because of its own logfiles.

It would, but I independently discovered the same thing. However, I
think that when this last happened, deleting the logs didn't fix it,
but I'm not sure. In any case, I'm now using KTorrent, but not
because of this bug, and I highly recommend it.

On 1/3/07, Oliver Doepner <email address hidden> wrote:
> It seems highly unlikely to me that Azureus would crash because of its
> own logfiles.
>
> --
> Azureus crashes with SIGSEGV
> https://launchpad.net/bugs/71220
>

ricmik (richard-waypoints) wrote :

Same thing here...
Azureus crashed, I deleted the logfiles and started it up.. Works great! :)
Annoying bug though..

arlen (arlen-abraham) wrote :

deleting the log files worked for me

Sasa Vilic (sasavilic) wrote :

Deleting the log files worked also for me.

Ubuntu 7.04 with latest updates.
Java 1.6
Azureus 2.5.0.0

Had same problem. Azureus Crashed after shutdown caused by battery problem.
Deleting Log files (in ~/.azureus/ ; ~/.azureus/logs ; ~/.azureus/logs/save) worked.

Ubuntu 7.04
java 1.6
Azureus 2.5.0.0

erimar77 (erimar77) wrote :

I'll have to agree, deleting the log files also worked for me. Here's the output of the crash:

eric@ericpc:~$ azureus
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)'
/nfs/grubsserv/home/eric/.gtkrc-2.0:2: error: scanner: unterminated string constant - e.g. `style'
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00000000, pid=18499, tid=3084352400
#
# Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode, sharing)
# Problematic frame:
# C 0x00000000
#
# An error report file with more information is saved as hs_err_pid18499.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted (core dumped)

reef (renzo-mischianti) wrote :

Same problem same solution in Ubuntu Gutsy (all java virtual machine)..
every same days the problem return....

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

Other bug subscribers