Bug 590334

Summary: [abrt] crash in java-1.6.0-openjdk-1:1.6.0.0-37.b17.fc13: Process /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: jimmyb
Component: java-1.6.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: asu, dbhole, james.brown, jpechane, lkundrak, mjw, rruss
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:cf58ef75fca5efa12a81c4f5a08456f975a8f520
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-28 16:51:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description jimmyb 2010-05-08 22:02:40 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/lib/i386/../../bin/java sun.applet.PluginMain
comment: I think this is from an issue accessing vista.ncsu.edu, although can't be positive...
component: java-1.6.0-openjdk
executable: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre/bin/java
global_uuid: cf58ef75fca5efa12a81c4f5a08456f975a8f520
kernel: 2.6.33.3-72.fc13.i686.PAE
package: java-1.6.0-openjdk-1:1.6.0.0-37.b17.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)
Comment 1 jimmyb 2010-05-08 22:02:42 UTC 
Created attachment 412577 [details]
File: backtrace
Comment 2 Andrew Su 2010-06-18 18:16:41 UTC 
Hello Jimmy,

This site requires a login, is there a way to reproduce this from the outside without logging if credentials cannot be provided.

Looking at your backtrace, could you upload the java error log, it should be located in your home directory. "/home/jabrown/hs_err_pid23518.log". since the backtrace contains a lot of missing information.

Thanks,
-Andrew
Comment 3 James G. Brown III 2010-06-18 18:34:50 UTC 
Andrew, I don't think I've reproduced elsewhere, but will see if you can on that site without logging in. I'll upload the file you are asking for when I get home. 

- James
Comment 4 Deepak Bhole 2011-03-28 16:51:39 UTC 

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