SIGSEV in JRE quits vuze [on loss of connection ]
Bug #571094 reported by
Vish
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
azureus (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Lucid |
Won't Fix
|
Undecided
|
Unassigned | ||
Maverick |
Won't Fix
|
Undecided
|
Unassigned | ||
openjdk-6 (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Lucid |
Won't Fix
|
Undecided
|
Unassigned | ||
Maverick |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Over the past few weeks , vuze has been quitting at random , and loss of connectivity , is mostly what triggers this..
And vuze just quits/crashes.
I didnt file a bug as this has been occurring at random , finally noticed this ~/hs_err_
It mentions the bug in JRE Hence reporting it here.
summary: |
- SIGSEV in JRE quits vuze + SIGSEV in JRE quits vuze [on loss of connection ] |
description: | updated |
tags: |
added: regression-release removed: regression-potential |
To post a comment you must log in.
Vuze keeps crashing after upgrade from 9.10 to 10.04
Also libswt- glx-gtk- 3.4-jni was installed - -3D view was not working
Installed libswt- glx-gtk- 3.5-jni - 3D view is OK
DEBUG::Tue May 04 12:30:53 CEST 2010 Data Missing /med/mai/ Inb/New/ Jim.com ] Mov/Hil/ Hil corba.se. impl.ior. IORImpl getProfile CORBA.INV_ OBJREF: vmcid: SUN minor code: 1201 completed: No
DEBUG::Tue May 04 12:30:57 CEST 2010 Data Missing /med/sda/
May 4, 2010 12:31:00 PM com.sun.
WARNING: "IOP00511201: (INV_OBJREF) IOR must have at least one IIOP profile"
org.omg.
# c24c98, pid=5573, tid=140375392184064 so.6+0x37c98] XQueryExtension +0x28 /bugs.launchpad .net/ubuntu/ +source/ openjdk- 6/
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fab61
#
# JRE version: 6.0_18-b18
# Java VM: OpenJDK 64-Bit Server VM (14.0-b16 mixed mode linux-amd64 )
# Derivative: IcedTea6 1.8
# Distribution: Ubuntu lucid (development branch), package 6b18-1.8-0ubuntu1
# Problematic frame:
# C [libX11.
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https:/
#