Created attachment 944018 [details] core_backtrace java got killed by SIGABRT. Version-Release number of selected component (if applicable): java-1.8.0-openjdk-headless-1.8.0.20-12.b26.fc21 How reproducible: I don't know. This happened only once to me. Additional info: This is a regression from F20 where I never ran into this bug. Since josm doesn't provide native code this is a bug in java. See https://josm.openstreetmap.de/ for josm binaries. Since abrt is unable to report this automatically I am doing it here: cmdline: java -Djosm.home=~/.local/share/josm -jar /home/christian/.local/lib/JOSM/josm-tested.jar executable: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.20-12.b26.fc21.x86_64/jre/bin/java kernel: 3.16.3-302.fc21.x86_64 uid: 1000
Created attachment 944019 [details] cgroup
Created attachment 944020 [details] dso_list
Created attachment 944021 [details] environ
Created attachment 944022 [details] limits
Created attachment 944023 [details] maps
Created attachment 944025 [details] open_fds
Created attachment 944026 [details] proc_pid_status
Hi Christian, thank you for taking the time to report this crash and sorry for the troubles with ABRT. It could be also useful to provide a GDB backtrace. If you still have the crash data directory on your disk, go to that directory, run 'abrt-action-perform-ccpp-analysis' and attach 'backtrace' file here.
Created attachment 944170 [details] backtrace as requested installing yum fixed the problem with abrt.
Hi Christian, is the problem with the JDK continuing then? If it happened only once, there is not much we can do as the trace does not provide enough information unfortunately.
No, I didn't run into this java bug any more, seems to have happened only once.
Ok, I was wrong, it happened again. This time it happened twice with JDownloader 2 beta running under GNOME/Wayland: 1. when clicking the "update now" button 2. when hiding the info/about dialog In both cases java crashed with SIGABRT. abrt/libreport is unable to report the issue, error message: »Validation failed: Element 'stacktrace' is invalid: List element is invalid: Element 'frames' is invalid: List element is invalid: Element 'file_name' is missing« reporter-ureport failed with exit code 1 Do you need more data? Which files?
And another SIGABRT running under GNOME/Wayland. This time it happened while MediathekView tried to start. Java crashed while MediathekView was loading the film list.
I can now reproduce this bug by following these steps: 1. log in to gnome-session-wayland-session 2. start JDownloader 2 (with default, i.e. X11 backend) 3. press on the "add links" button which should do some clipboard access Then java crashes.
I'll try to look at that, but I don't think Wayland is in anyway supported by OpenJDK at this stage.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.