Version-Release number of selected component:
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
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-18.104.22.168.x86_64/jre/lib/amd64/server/libjvm.so
Potential duplicate: bug 829801
Created attachment 758765 [details]
Created attachment 758766 [details]
Created attachment 758767 [details]
Created attachment 758768 [details]
Created attachment 758769 [details]
Created attachment 758770 [details]
Created attachment 758771 [details]
Created attachment 758772 [details]
Created attachment 758773 [details]
Created attachment 758774 [details]
Created attachment 758775 [details]
Created attachment 758776 [details]
Is this reproducible?
(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.
Created attachment 759325 [details]
custom made vuze.service
What is the best to reproduce it consistently?
Run azureus , the Java crashes out every day.
That's what happens me.
I think it's the only Java app, I use.
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.
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.
I would like to leave bz open for a week to monitor?
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).
Yes, I think this can be closed. Only 2 crashes since.
It is still crashing? Do you have a trace for the crash?
Created attachment 765440 [details]
abrt freezing on me, but found this in /tmp/jvm-22728 from yesterday
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.