Version-Release number of selected component: java-1.8.0-openjdk-devel-1.8.0.25-5.b18.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 3 cmdline: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.x86_64/bin/java -Dfile.encoding=UTF-8 -classpath /home/nice/workspace/CdDatabase/bin:/usr/lib64/javasqlite/sqlite.jar:/home/nice/git/jaudiotagger/target/jaudiotagger-2.2.2.jar CdDatabase cd 719 crash_function: oopDesc::print_on executable: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.x86_64/bin/java kernel: 3.17.7-300.fc21.x86_64 runlevel: N 3 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (9 frames) #0 oopDesc::print_on at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.x86_64/jdk8/hotspot/src/share/vm/oops/oop.cpp:43 #1 os::print_register_info at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.x86_64/jdk8/hotspot/src/os_cpu/linux_x86/vm/os_linux_x86.cpp:841 #2 VMError::report at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.x86_64/jdk8/hotspot/src/share/vm/utilities/vmError.cpp:541 #5 signalHandler at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.x86_64/jdk8/hotspot/src/os/linux/vm/os_linux.cpp:4257 #7 memmove at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:1021 #8 Unsafe_CopyMemory2 at /usr/src/debug/java-1.8.0-openjdk-1.8.0.25-5.b18.fc21.x86_64/jdk8/hotspot/src/share/vm/prims/unsafe.cpp:688 #9 ?? #10 ?? #11 ??
Created attachment 977642 [details] File: backtrace
Created attachment 977643 [details] File: cgroup
Created attachment 977644 [details] File: core_backtrace
Created attachment 977645 [details] File: dso_list
Created attachment 977646 [details] File: environ
Created attachment 977647 [details] File: exploitable
Created attachment 977648 [details] File: hs_err.log
Created attachment 977649 [details] File: limits
Created attachment 977650 [details] File: maps
Created attachment 977651 [details] File: open_fds
Created attachment 977652 [details] File: proc_pid_status
Created attachment 977653 [details] File: var_log_messages
Hi, how can we reproduce this issue?
I'm not really sure. I wrote a program which reads mp3 tags from data cds and stores those in a sqlite database. It crashed during this process. I reran the program and it did crash again but not on the same file, so it doesn't seem to be a problem with a specific file. I suspect the cd has degraded a bit since the cd reader seemed to be struggling a little bit to read the information.
Andrew, based on the above, can we pinpoint what the issue might be?
(In reply to Deepak Bhole from comment #15) > Andrew, based on the above, can we pinpoint what the issue might be? Maybe. Some program is calling Unsafe.copyMemory() but the backtrace doesn't say who that is. Unsafe.copyMemory() can trash absolutely anything, as its name suggests. If we could get a decent backtrace we'd know.
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.