JNA造成EXCEPTION_ACCESS_VIOLATION？ [英] JNA causing EXCEPTION_ACCESS_VIOLATION?

问题描述

我的Java UI意外终止和倾倒的 hs_err_pid 文件。该文件说：这次事故发生在本地code中的Java虚拟机之外。 JNA是唯一的本土code，我们使用。有谁知道任何知道的问题或错误与任何JNA版本可能会导致这样。我已经包含了一些从下面的错误文件的内容。

 已经由Java运行时环境检测到意外的错误：EXCEPTION_ACCESS_VIOLATION（0000005）在PC = 0x6d02bcbd，PID = 312，TID = 3616 Java虚拟机：Java的热点（TM）客户机VM（11.0-B16混合模式，共享Windows的x86）的＆LT; BR＆GT;
 问题的框架：
 C [awt.dll + 0x2bcbd] 如果您想提交错误报告，请访问：
   http://java.sun.com/webapps/bugreport/crash.jsp
 该事故发生在Java虚拟机之外的本土code。
 请参阅何处报告的bug问题的框架。当前线程（0x02acf000）：JavaThreadAWT-Windows的守护[_thread_in_native，ID = 3616，栈（0x02eb0000,0x02f00000）SIGINFO：异常code = 0000005，写地址0xe2789280
寄存器：
EAX = 0x234f099c，EBX = 0x00001400，ECX = 0x00000100，EDX = 0xe2789280
ESP = 0x02eff4a4，EBP = 0x00000400时，ESI = 0x234f099c，EDI = 0xe2789280
EIP = 0x6d02bcbd，EFLAGS = 0x00010206栈顶：（SP = 0x02eff4a4）
0x02eff4a4：02eff500 00000100 00000100 02eff584
0x02eff4b4：6d0a5697 00000400 00000400 00000100
0x02eff4c4：00000100 02eff700 02eff500 00000000
0x02eff4d4：00000000 00000100 00000100 041ac3a0
0x02eff4e4：00182620 00000400 00000000 e2789280
0x02eff4f4：00000000 00000100 00000100 00000000
0x02eff504：00000000 00000100 00000100 00000000
0x02eff514：00000000 00000004 00000400 00000000说明：（PC = 0x6d02bcbd）
0x6d02bcad：00 00 00 8b中4c中24 14 8b的E9 C1 E9 02 8b的F0 8b中发
0x6d02bcbd：F3 A5 8B CD 83 E1 03 F3 A4 8B 74 24 18 8B 4C 24堆栈：[0x02eb0000,0x02f00000]，SP = 0x02eff4a4，自由空间= 317K
本机框架：（J =已编译的Java code，J =间preTED，VV = VM code，C =本地code）
C [awt.dll + 0x2bcbd][错误报告（打印本地堆栈）过程中发生错误时，编号0000005]Java的框架：（J =已编译的Java code，J =间preTED，VV = VM code）
Ĵsun.awt.windows.WToolkit.eventLoop（）V + 0
Ĵsun.awt.windows.WToolkit.run（）V + 69
Ĵjava.lang.Thread.run（）V + 11
V〜StubRoutines :: call_stub
 

解决方案

我只打了同样的错误，这是apppearantly在新的Direct3D的错误与1.6.0_11与低显存机发生加速的Java2D功能。
如果你开始-Dsun.java2d.d3d您的应用程序=假应该再工作。
太阳Bug跟踪这是以下几点： http://bugs.sun.com/view_bug。怎么办？bug_id = 6788497

My Java UI unexpectly terminated and dumped an hs_err_pid file. The file says "The crash happened outside the Java Virtual Machine in native code." JNA is the only native code we use. Does anyone know of any know issues or bugs with any JNA version that might cause this. I've included some of the contents from the error file below.

An unexpected error has been detected by Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d02bcbd, pid=312, tid=3616

 Java VM: Java HotSpot(TM) Client VM (11.0-b16 mixed mode, sharing windows-x86)<br>
 Problematic frame:
 C  [awt.dll+0x2bcbd]

 If you would like to submit a bug report, please visit:
   http://java.sun.com/webapps/bugreport/crash.jsp
 The crash happened outside the Java Virtual Machine in native code.
 See problematic frame for where to report the bug.

Current thread (0x02acf000):  JavaThread "AWT-Windows" daemon [_thread_in_native, id=3616, stack(0x02eb0000,0x02f00000)]

siginfo: ExceptionCode=0xc0000005, writing address 0xe2789280


Registers:
EAX=0x234f099c, EBX=0x00001400, ECX=0x00000100, EDX=0xe2789280
ESP=0x02eff4a4, EBP=0x00000400, ESI=0x234f099c, EDI=0xe2789280
EIP=0x6d02bcbd, EFLAGS=0x00010206

Top of Stack: (sp=0x02eff4a4)
0x02eff4a4:   02eff500 00000100 02eff584 00000100
0x02eff4b4:   6d0a5697 00000400 00000400 00000100
0x02eff4c4:   00000100 02eff700 02eff500 00000000
0x02eff4d4:   00000000 00000100 041ac3a0 00000100
0x02eff4e4:   00182620 00000400 e2789280 00000000
0x02eff4f4:   00000000 00000100 00000100 00000000
0x02eff504:   00000000 00000100 00000100 00000000
0x02eff514:   00000000 00000004 00000400 00000000

Instructions: (pc=0x6d02bcbd)
0x6d02bcad:   00 00 00 8b 4c 24 14 8b e9 c1 e9 02 8b f0 8b fa
0x6d02bcbd:   f3 a5 8b cd 83 e1 03 f3 a4 8b 74 24 18 8b 4c 24

Stack: [0x02eb0000,0x02f00000],  sp=0x02eff4a4,  free space=317k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [awt.dll+0x2bcbd]

[error occurred during error reporting (printing native stack), id 0xc0000005]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  sun.awt.windows.WToolkit.eventLoop()V+0
j  sun.awt.windows.WToolkit.run()V+69
j  java.lang.Thread.run()V+11
v  ~StubRoutines::call_stub

解决方案

I just hit that very same bug, it's apppearantly a bug in the new Direct3d accelerated Java2d functionality with 1.6.0_11 that happens with machines with low video ram. If you start your app with -Dsun.java2d.d3d=false it should work again. The sun bug tracking this is the following: http://bugs.sun.com/view_bug.do?bug_id=6788497

这篇关于JNA造成EXCEPTION_ACCESS_VIOLATION？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！