JDK-6487931 : JVM reports EXCEPTION_FLT_STACK_CHECK when calling a Java method through JNI
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 5.0u9,6
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000,windows_xp
  • CPU: x86
  • Submitted: 2006-10-30
  • Updated: 2022-10-17
  • Resolved: 2011-03-07
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other Other JDK 6 JDK 7 Other
1.4.2_19-rev,hs11Fixed 1.4.2_21Fixed 6u4Fixed 7Fixed hs11Fixed
Related Reports
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
Operating System
O.S version: Windows 2000 Server and Windows 2003 Server 

Product Name: Java
Product version:  1.5.0_09-b01 and 1.5.0_06-b05

Hardware platform: 
Microsoft Windows 2000 Server
5.0.2195 Service Pack 4 Build 2195
Dell Precision WorkStation 530 MT 
Processor (2)	x86 Family 15 Model 2 Stepping 4 GenuineIntel ~2174 Mhz
Physical Memory 1,047,564 KB

Microsoft Windows Server 2003 Enterprise Edition
5.2 Service Pack 1 (Build 3790)
Machine Type AT/AT Compatible
Processor x86 Family 15 Model 0 Stepping 10
Physical Memory 1024 MB
 

JVM reports EXCEPTION_FLT_STACK_CHECK when calling a Java method through
JNI.  A java core file is attached.

 <<hs_err_pid4348.log>> 

Problem has a short term workaround, creating a .hotspotrc file which
includes the following prevents the EXCEPTION_FLT_STACK_CHECK 

-XX:CompileCommand=exclude,com/documentum/fc/tracing/impl/Tracing,isEnabled


Full problem description:

Here's what  -XX:+PrintCompilation shows just prior to the error

 54   b   java.lang.Class::forName (36 bytes)
 55   b   java.util.HashMap::maskNull (12 bytes)
 56   b   java.util.HashMap::hash (36 bytes)
 57   b
com.documentum.fc.tracing.impl.aspects.BaseTracingAspect::ajc$if_0 (4
bytes)

 58   b   com.documentum.fc.tracing.impl.Tracing::isEnabled (4 bytes)
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_FLT_STACK_CHECK (0xc0000092) at pc=0x01270618, pid=5684,
tid=5008
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# v  ~RuntimeStub::init_check_patching Runtime1 stub
#
# An error report file with more information is saved as
hs_err_pid5684.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

If customer passes

-XX:CompileCommand=exclude,com/documentum/fc/tracing/impl/Tracing,isEnabled 
to the Java VM initialization the problem does not reproduce.  

The method isEnabled is implemented as

    protected static synchronized Tracer getTracer()  {
        return s_tracer;
    }

The program showing this error is part of customer product namely dmbasic.
This program compiles and executes Basic programs which support
extensions specific to our products.  One such extension is the ability
to invoke a Java method from Basic.  The stack trace in the
hs_err_pid...log file shows calls in dmbasic and DOCNPB22.dll (a third party product that supports compiling and running Basic programs).  
Customer can provide a copy of dmbasic.exe, docnpb22.dll and our dfc.jar file that will reproduce the problem on Windows platforms.

We need to see why it is causing the problem.

Attached Files : 
===================
1)  call831047.zip  contains a full windows dump, a copy of the output generated (with -verbose:jni and -Xcheck:jni) and a copy of the main executable PDB file.
2)  hs_err_pid4348.log - Hotspot error logs.

Comments
EVALUATION Since 6.0 is going to release, this bug could be fixed in 6.0u01.
31-10-2006