windows search for file type stack overflow

You can find JRE libraries in the jre/lib or jre/bin directories of the JRE distribution. If so, gather as much data as possible and submit a bug or report, indicating the library name. If the native library where the crash occurred is part of the Java Runtime Environment (JRE) (for example awt.dll, net.dll, and so forth), then it is possible that you have encountered a library or API bug.

If the native library has been provided by another vendor and is used by your application, then file a bug report against this third-party application and provide the fatal error log information. A significant number of issues with JNI code can be identified by running the application with the -Xcheck:jni option added to the command line. If the native library is provided by your application, then investigate the source code of your native library. The first step to solving a crash in a native library is to investigate the source of the native library where the crash occurred. In this case, although the problematic frame is a VM frame, the thread stack shows that a native routine in App.dll has called into the VM (probably with JNI).

Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)Ĭ <= C/native frame T H R E A D -Ĭurrent thread (0x00036960): JavaThread 'main' # Java VM: Java HotSpot(TM) Client VM (1.5-internal mixed mode) # An unexpected error has been detected by HotSpot Virtual Machine:

Windows search for file type stack overflow