I'd rather reproduce this problem with a GCC 5 compiled openjdk in order to rule out ABI problems. With bug 1208369 fixed I think I'll be able to make some progress on this one. > out till you figure out what's going on. ![]() Let me know if you want to keep this patch > more consistently, so it might be a good way to observe this behaviour. > spews out thousands of errors and it also seemed to cause the crash a bit Running the above compilation command under valgrind > and it crashed eventually, indicating that the patch only seems to make the > -d /root/rpmbuild/BUILD/plplot-5.10.0/fedora/bindings/java do true done > /root/rpmbuild/BUILD/plplot-5.10.0/fedora/bindings/java > I ran this in an infinite loop with the patch reverted (and in fact, with > closely, it looks like the segfault does not always happen and is likely > and the segfault indeed seemed to go away at first glance. > malloc: Consistently apply trim_threshold to all heaps (In reply to Siddhesh Poyarekar from comment #8) Otherwise I'll rebase by the end of the week. Let me know if you want to keep this patch out till you figure out what's going on. ![]() Running the above compilation command under valgrind spews out thousands of errors and it also seemed to cause the crash a bit more consistently, so it might be a good way to observe this behaviour. While javac -classpath /root/rpmbuild/BUILD/plplot-5.10.0/fedora/bindings/java /root/rpmbuild/BUILD/plplot-5.10.0/fedora/bindings/java/plplotjavacJNI.java -d /root/rpmbuild/BUILD/plplot-5.10.0/fedora/bindings/java do true doneĪnd it crashed eventually, indicating that the patch only seems to make the crash more frequent. I ran this in an infinite loop with the patch reverted (and in fact, with -10.fc23): However, looking closely, it looks like the segfault does not always happen and is likely some kind of race condition. Malloc: Consistently apply trim_threshold to all heaps Īnd the segfault indeed seemed to go away at first glance. But if it's not trivial to fix, I'd suggest untagging latest glibc as temporary workaround. I don't know whether the bug is in openjdk or glibc. Rebuild any Java package in mock or koji. ![]() The failures are random, but tend to be reproducible for any build that runs more than few seconds.ġ. Version-Release number of selected component (if applicable):ġ:java-1.8.0-openjdk-1.8.0.22 I assume that libpng is not relevant here. (Daemon) Server detected as crashed! Attempting to reboot server now.Java applications started randomly crashing with SIGSEGV after minor version update of glibc from 2.21.90-8.fc23 to 2.21.90-9.fc23.Īccording to koschei, the only dependency change since previous succesful build was glibc and libpng. entrypoint.sh: line 15: 65 Segmentation fault (core dumped) java -Xms128M -Xmx32768M -jar server.jar # instructions on how to reproduce the bug and visit: # If you would like to submit a bug report, please include # An error report file with more information is saved as: Default location: /home/container/core or core.65 ![]() # Distribution: Custom build (Tue Nov 21 11:22:) # Java VM: OpenJDK 64-Bit Server VM (25.151-b12 mixed mode linux-amd64 ) # A fatal error has been detected by the Java Runtime Environment: The server runs for a few minutes then it crashes. I just changed server hostings and when I did I started to get this error when I started to use the latest 1.12.2 build.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |