Java Crashed application - how to read the crash file created by the JVM?

Question

I have a java application and it started to swear, without exception. But sometimes the JVM creates a crash log file that has a name like "hs_err_pid10930.log". Can anyone read this and tell me what's wrong? I can’t understand what happened. The only reasonable information that I find here is that the swap size is 0. Am I a problem? How could this happen?

You can find the file here: http://chessfriends-release.s3.amazonaws.com/logs/hs_err_pid10930.log?AWSAccessKeyId=AKIAJP5BYGKOCMCDVZHA&Expires=1305128715&Signature=XEZMuJ0xNSM6YTcdwsI3ah04I4h04i

Thanks.

Libor

Answer 1

Whenever you get such a crash, a Java programmer almost never fails because the JVM crashes, which should not be. Looking at the log file, it looks like somewhere in the JJ OpenJDK; I do not know what specifically causes this. I would suggest you try Oracle JDK, not OpenJDK.

I am not a specialist in reading these types of crash dumps, but this is the part that I use to determine what causes the problem:

# Problematic frame: # V [libjvm.so+0x64d62d] 

This is at the top of the dump. This is not always libjvm.so; I saw some with libGL.so.

If you want to write an error, the dump includes the following statement:

 # If you would like to submit a bug report, please include # instructions how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ 

I do not know what you are doing, which leads to a failure, and there may be a workaround. But under no circumstances does the JVM fail, so this is a bug in the JVM that you are using.

Edit
The log states that you are using Ubuntu 9.10; there have been two releases of Ubuntu since then, so I doubt the error will be useful if you don't check it on Ubuntu 10.04 or 10.10. I don’t know if you can upgrade to a newer version, but your problem may already be fixed.