Hide Forgot
Description of problem: upgraded F19 > F20 this morning. Azureus started by azvuze.service (custom service unit). a number of crash\restarts have happened since. Version-Release number of selected component: java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 3 cmdline: java -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on -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: os::abort executable: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/jre-abrt/bin/java kernel: 3.11.3-301.fc20.x86_64+debug runlevel: N 5 type: CCpp uid: 1005 Truncated backtrace: Thread no. 1 (10 frames) #2 os::abort at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/os/linux/vm/os_linux.cpp:1594 #3 VMError::report_and_die at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/share/vm/utilities/vmError.cpp:1053 #4 JVM_handle_linux_signal at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/os_cpu/linux_x86/vm/os_linux_x86.cpp:531 #6 ?? #7 hash_insert at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/share/vm/opto/phaseX.cpp:195 #8 NodeHash::grow at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/share/vm/opto/phaseX.cpp:289 #9 check_grow at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/share/vm/opto/phaseX.hpp:76 #10 NodeHash::hash_find_insert at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/share/vm/opto/phaseX.cpp:148 #11 hash_find_insert at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/share/vm/opto/phaseX.hpp:352 #12 PhaseIterGVN::transform_old at /usr/src/debug/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/openjdk/hotspot/src/share/vm/opto/phaseX.cpp:1130 Potential duplicate: bug 853621
Created attachment 808808 [details] File: backtrace
Created attachment 808809 [details] File: cgroup
Created attachment 808810 [details] File: core_backtrace
Created attachment 808811 [details] File: dso_list
Created attachment 808812 [details] File: environ
Created attachment 808814 [details] File: hs_err.log
Created attachment 808815 [details] File: limits
Created attachment 808816 [details] File: maps
Created attachment 808817 [details] File: open_fds
Created attachment 808818 [details] File: proc_pid_status
Created attachment 808819 [details] File: var_log_messages
Is this error reproducible?
(In reply to Deepak Bhole from comment #12) > Is this error reproducible? I would have to check as I'm still getting crashes in java-openjdk just ignoring them, will have a check for any marked os abort.
Running Upstream Vuze or Fedora-Azureus Openjdk crahes are a regular occurance. At times only minutes apart. Waiting on a new core2 quad cpu, to see if it will help. (needed for kernel problems anyway) Have a sligthtly modified script version 2 for vuze, and a custom.servce file to always restart, combined with a java process scipt. Will upload all to bz, when ready. reporter: libreport-2.1.8 backtrace_rating: 3 cmdline: java -agentpath:/usr/lib64/libabrt-java-connector.so=abrt=on -Xmx1028m -cp ./Azureus2.jar:./swt.jar -Djava.library.path=/home/frank/Upstream_Vuze -Dazureus.config.path=/home/frank/Upstream_Vuze/.azureus -Dazureus.install.path=/home/frank/Upstream_Vuze -Dazureus.script=/home/frank/Upstream_Vuze/azureus -Dazureus.script.version=3 org.gudy.azureus2.platform.unix.ScriptBeforeStartup crash_function: os::abort executable: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/jre-abrt/bin/java kernel: 3.11.4-301.fc20.x86_64+debug package: java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20 reason: Process /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.60-2.4.2.9.fc20.x86_64/jre-abrt/bin/java was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1005
(In reply to Deepak Bhole from comment #12) > Is this error reproducible? > Have a sligthtly modified script version 2 for vuze, and a custom.service typo script version 3 crashesx3 occurances for this bz this morning alone, using upstream vuze. Will start re-checking with fedora supplied azureus.
Created attachment 811549 [details] check for java script checks for java without vuze\azureus and kills if zombie.
Created attachment 811550 [details] Upstream Vuze .service file
Created attachment 811551 [details] tells me if azureus \vuze down If azureus \ vuze no process, is then invokes the java sighup script.
Created attachment 811567 [details] fedora /usr/bin/azureus has fix from bz 979102 included
Created attachment 811568 [details] Upstream vuze script Modified to not overwrite Fedora-Azureus configs
Created attachment 811572 [details] another hs_jvm log Am guessing it's the same bug. This time I started fedora-azureus from terminal /usr/bin/azureus (enter) got this log plus a 450+mb core.4015 file
This is the core file from comment 21 (big) http://www.frankly3d.eu/fedora/core.4195
Thanks for the core Frank. The issue is arising in SWT/JNI code that is outside of JVM control. Re-assigning to swt owner.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.