# An unexpected error has been detected by HotSpot Virtual Machine: Consider the extract in the following example from the header of a fatal error log. The crash could be caused by something else, but analysis of the library and any core file or crash dump is a good starting place. If the fatal error log indicates the problematic frame to be a native library, then there might be a bug in the native code or the Java Native Interface (JNI) library code.
Microsoft Visual C++ Version Considerations This chapter contains the following sections: See Fatal Error Log for an explanation of how to locate this file, as well as a detailed description of the file.
This is a text file that the Java HotSpot VM generates in the event of a crash. In general, the first step with any crash is to locate the fatal error log. This chapter provides suggestions about how to examine a crash and work around some of the issues (if possible) until the cause of the bug is diagnosed and fixed. External factors, such as resource exhaustion in the OS can also cause a crash.Ĭrashes caused by bugs in the Java HotSpot VM or in the Java SE library code are rare. For example, a crash can occur due to a bug in the Java HotSpot VM, in a system library, in a Java SE library or an API, in application native code, or even in the operating system (OS). There are various possible reasons for a crash. Information and guidance about some specific procedures for troubleshooting system crashes.Ī crash, or fatal error, causes a process to terminate abnormally.
0 kommentar(er)
