Bug 641416 - [abrt] java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
Summary: [abrt] java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13: Process /usr/lib/jvm/java-1....
Keywords:
Status: CLOSED DUPLICATE of bug 688453
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Denis Lila
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cbe683451e4688bd0744c9c6270...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-08 16:08 UTC by Norberto
Modified: 2011-03-28 20:58 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-28 20:58:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (19.59 KB, text/plain)
2010-10-08 16:08 UTC, Norberto
no flags Details

Description Norberto 2010-10-08 16:08:41 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: java -Dazureus.install.path=/home/norberto/.azureus/app -Dazureus.script.version=2 -Dazureus.script=/usr/bin/azureus org.gudy.azureus2.ui.swt.Main
component: java-1.6.0-openjdk
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java
kernel: 2.6.34.7-56.fc13.i686
package: java-1.6.0-openjdk-1:1.6.0.0-42.b18.fc13
rating: 4
reason: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1286488309
uid: 500

Comment 1 Norberto 2010-10-08 16:08:45 UTC
Created attachment 452375 [details]
File: backtrace

Comment 2 Omair Majid 2010-10-08 16:15:04 UTC
Is this error reproducible? Did it start happening recently? Can you please describe how to make this crash happen? This looks like a real bug in the JDK but unless I can reproduce it locally, I wont be able to fix it.

Comment 3 Denis Lila 2011-03-28 20:58:15 UTC

*** This bug has been marked as a duplicate of bug 688453 ***


Note You need to log in before you can comment on or make changes to this bug.