#
# An unexpected error has been detected by Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x2d7855f0, pid=6120, tid=7348
#
# Java VM: Java HotSpot(TM) Client VM (11.0-b16 mixed mode windows-x86)
# Problematic frame:
# C 0x2d7855f0
#
# 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.
#
--------------- T H R E A D ---------------
Current thread (0x27758000): JavaThread "AWT-Windows" daemon [_thread_in_native, id=7348, stack(0x27e30000,0x27f30000)]
siginfo: ExceptionCode=0xc0000005, ExceptionInformation=0x00000008 0x2d7855f0
Registers:
EAX=0x2d785640, EBX=0x0019e700, ECX=0x2d785618, EDX=0x00150608
ESP=0x27f2f890, EBP=0x27f2f8b4, ESI=0x4f1e138c, EDI=0x00000001
EIP=0x2d7855f0, EFLAGS=0x00010206
Top of Stack: (sp=0x27f2f890)
0x27f2f890: 4f1a884f 00000001 0019e478 001d1be8
0x27f2f8a0: 0019e210 0019e478 27f2f920 4f1d9c99
0x27f2f8b0: ffffffff 27f2f8c8 4f1a76a0 4f1e138c
0x27f2f8c0: 0006040f 00000000 27f2f8e4 76182fb5
0x27f2f8d0: 0006040f 00000000 00009812 27758114
0x27f2f8e0: 00000001 27f2f8f8 76183729 0006040f
0x27f2f8f0: e00e0804 00000000 27f2f92c 6d096a87
0x27f2f900: 0006040f 27f2f9a4 6d0966d0 00000000
这种问题大部分情况下是虚拟机底层bugs导致了未知的内存问题。
我在一次工作中,使用exe4j打包好的swing程序运行过程中总之不时的报这种异常,结果当我在配置exe4j的时候加上了"-Xms128m -Xmx256m"后,这问题竟然没有了。
在此分享一下,如果你也碰到这种问题,不妨也试试这种办法。
# An unexpected error has been detected by Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x2d7855f0, pid=6120, tid=7348
#
# Java VM: Java HotSpot(TM) Client VM (11.0-b16 mixed mode windows-x86)
# Problematic frame:
# C 0x2d7855f0
#
# 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.
#
--------------- T H R E A D ---------------
Current thread (0x27758000): JavaThread "AWT-Windows" daemon [_thread_in_native, id=7348, stack(0x27e30000,0x27f30000)]
siginfo: ExceptionCode=0xc0000005, ExceptionInformation=0x00000008 0x2d7855f0
Registers:
EAX=0x2d785640, EBX=0x0019e700, ECX=0x2d785618, EDX=0x00150608
ESP=0x27f2f890, EBP=0x27f2f8b4, ESI=0x4f1e138c, EDI=0x00000001
EIP=0x2d7855f0, EFLAGS=0x00010206
Top of Stack: (sp=0x27f2f890)
0x27f2f890: 4f1a884f 00000001 0019e478 001d1be8
0x27f2f8a0: 0019e210 0019e478 27f2f920 4f1d9c99
0x27f2f8b0: ffffffff 27f2f8c8 4f1a76a0 4f1e138c
0x27f2f8c0: 0006040f 00000000 27f2f8e4 76182fb5
0x27f2f8d0: 0006040f 00000000 00009812 27758114
0x27f2f8e0: 00000001 27f2f8f8 76183729 0006040f
0x27f2f8f0: e00e0804 00000000 27f2f92c 6d096a87
0x27f2f900: 0006040f 27f2f9a4 6d0966d0 00000000
这种问题大部分情况下是虚拟机底层bugs导致了未知的内存问题。
我在一次工作中,使用exe4j打包好的swing程序运行过程中总之不时的报这种异常,结果当我在配置exe4j的时候加上了"-Xms128m -Xmx256m"后,这问题竟然没有了。
在此分享一下,如果你也碰到这种问题,不妨也试试这种办法。