Java Crash Analysis



Note that hs_err_pid.log files only get created if there is an actual JVM crash. If your application "only" quits due to an unhandled exception somewhere, then no such file will be created.

If the crash occurs as the result of a native stack overflow (typically resulting in a SIGSEGV as the application tries to read/write a stack guard page), no hs_err_pid file is generated on many platforms (e.g., Linux) since the process which creates the file cannot complete if you are out of stack space.

When a fatal error occurs an error log is created in the file hs_err_pid.log (where is the process id of the process). Where possible the file is created in the working directory of the process. In the event that the file cannot be created in the working directory (insufficient space, permission problem, or other issue) then the file is created in the temporary directory for the operating system. On Solaris and Linux the temporary directory is /tmp. On Windows the temporary directory is specified by the value of the TMP environment variable, or if that is not defined, the value of the TEMP environment variable.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License