Bug 972441

Summary: [abrt] java-1.7.0-openjdk-1.7.0.19-2.3.9.5.fc18: pthread_cond_wait@@GLIBC_2.3.2: Process /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64/jre/bin/java was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Frank Murphy <frankly3d>
Component: java-1.7.0-openjdkAssignee: Deepak Bhole <dbhole>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: ahughes, dbhole, jerboaa, jvanek, omajid
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1c4de2b9b9368d5d1da301b81a4ed0fec65aa345
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 21:44:27 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: hs_err.log
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: smolt_data
none
File: var_log_messages
none
custom made vuze.service
none
cat /var/log/messages | grep azureus
none
hs_error.log none

Description Frank Murphy 2013-06-09 12:27:43 UTC
Version-Release number of selected component:
java-1.7.0-openjdk-1.7.0.19-2.3.9.5.fc18

Additional info:
reporter:       libreport-2.1.4.26.gb03d
backtrace_rating: 4
cmdline:        java -Dazureus.install.path=/home/frank/.azureus/app -Dazureus.script.version=2 -Dazureus.script=/usr/bin/azureus -Dorg.eclipse.swt.browser.UseWebKitGTK=true org.gudy.azureus2.ui.swt.Main
crash_function: pthread_cond_wait@@GLIBC_2.3.2
executable:     /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64/jre/bin/java
kernel:         3.9.4-200.fc18.x86_64
uid:            1005
xsession_errors: 

Truncated backtrace:
Thread no. 82 (2 frames)
 #0 pthread_cond_wait@@GLIBC_2.3.2 at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:165
 #1 os::PlatformEvent::park() at /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64/jre/lib/amd64/server/libjvm.so

Potential duplicate: bug 829801

Comment 1 Frank Murphy 2013-06-09 12:27:47 UTC
Created attachment 758765 [details]
File: backtrace

Comment 2 Frank Murphy 2013-06-09 12:27:50 UTC
Created attachment 758766 [details]
File: cgroup

Comment 3 Frank Murphy 2013-06-09 12:27:54 UTC
Created attachment 758767 [details]
File: core_backtrace

Comment 4 Frank Murphy 2013-06-09 12:27:57 UTC
Created attachment 758768 [details]
File: dso_list

Comment 5 Frank Murphy 2013-06-09 12:28:01 UTC
Created attachment 758769 [details]
File: environ

Comment 6 Frank Murphy 2013-06-09 12:28:05 UTC
Created attachment 758770 [details]
File: hs_err.log

Comment 7 Frank Murphy 2013-06-09 12:28:08 UTC
Created attachment 758771 [details]
File: limits

Comment 8 Frank Murphy 2013-06-09 12:28:12 UTC
Created attachment 758772 [details]
File: maps

Comment 9 Frank Murphy 2013-06-09 12:28:15 UTC
Created attachment 758773 [details]
File: open_fds

Comment 10 Frank Murphy 2013-06-09 12:28:18 UTC
Created attachment 758774 [details]
File: proc_pid_status

Comment 11 Frank Murphy 2013-06-09 12:28:22 UTC
Created attachment 758775 [details]
File: smolt_data

Comment 12 Frank Murphy 2013-06-09 12:28:25 UTC
Created attachment 758776 [details]
File: var_log_messages

Comment 13 Deepak Bhole 2013-06-10 18:42:01 UTC
Is this reproducible?

Comment 14 Frank Murphy 2013-06-10 18:50:44 UTC
(In reply to Deepak Bhole from comment #13)
> Is this reproducible?

yes, the only way I can keep azureus on is with the following attached servcei.

Comment 15 Frank Murphy 2013-06-10 18:51:26 UTC
Created attachment 759325 [details]
custom made vuze.service

Comment 16 Deepak Bhole 2013-06-10 18:57:41 UTC
What is the best to reproduce it consistently?

Comment 17 Frank Murphy 2013-06-10 21:19:30 UTC
Run azureus , the Java crashes out every day.
That's what happens me.

Comment 18 Frank Murphy 2013-06-10 21:21:37 UTC
I think it's the only Java app, I use.

Comment 19 Frank Murphy 2013-06-11 11:57:24 UTC
Created attachment 759584 [details]
cat /var/log/messages | grep azureus

A bit more digging, azureus is crashing out probably causing Java to crash out?
Some path seems to not exist. Am attaching :
cat /var/log/messages | grep azureus

search for jvm-exports within attached file.

Comment 20 Frank Murphy 2013-06-13 09:08:01 UTC
May have gone now.
Two things, made symlink:


/usr/lib/jvm-exports/java-openjdk -> /etc/alternatives/jre_openjdk_exports

and an update to openjdk this morning.

java-1.7.0-openjdk-1.7.0.19-2.3.9.8.fc18.x86_64

I would like to leave bz open for a week to monitor?

Comment 21 Deepak Bhole 2013-06-17 15:41:10 UTC
Sure, that sounds good. Thank you for reporting back! (and sorry for the delay in response, I was away at the Red Hat Summit last week).

Comment 22 Frank Murphy 2013-06-25 11:46:23 UTC
Yes, I think this can be closed. Only 2 crashes since.

Comment 23 Deepak Bhole 2013-06-25 21:31:28 UTC
It is still crashing? Do you have a trace for the crash?

Comment 24 Frank Murphy 2013-06-26 07:49:51 UTC
Created attachment 765440 [details]
hs_error.log

abrt freezing on  me, but found this in /tmp/jvm-22728 from yesterday

Comment 25 Fedora End Of Life 2013-12-21 13:55:55 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 26 Fedora End Of Life 2014-02-05 21:44:27 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.