Java mks api 崩溃

Question

故事:我尝试使用 java mks api 连接到完整性，然后执行“si viewsandbox”命令。与完整性的连接和命令的执行工作正常，直到我用小沙箱尝试它。如果我在一个巨大的沙箱中尝试 viewsandbox 命令，我会收到以下错误日志:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000, pid=4984, tid=3628
#
# JRE version:  (7.0_40-b43) (build )
# Java VM: Java HotSpot(TM) Client VM (24.0-b56 mixed mode windows-x86 )
# Problematic frame:
# C  0x00000000
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

---------------  T H R E A D  ---------------

Current thread (0x0054dc00):  JavaThread "main" [_thread_in_Java, id=3628, stack(0x010a0000,0x10aa0000)]

siginfo: ExceptionCode=0xc0000005, ExceptionInformation=0x00000008 0x00000000

Registers:
EAX=0x00100000, EBX=0x52aada90, ECX=0x12aa0da0, EDX=0x00500001
ESP=0x10a9edf0, EBP=0x10a9ee18, ESI=0x10a9edf4, EDI=0x10a9ee1c
EIP=0x00000000, EFLAGS=0x00010216

Top of Stack: (sp=0x10a9edf0)
0x10a9edf0:   10aa347b 12aa0da0 10a9edf8 52ab76ab
0x10a9ee00:   10a9ee1c 52b0d648 00000000 52ab76e8
0x10a9ee10:   10a9edf4 10a9ee20 10a9ee3c 10aa03d7
0x10a9ee20:   10a9ee70 10a9ee4c 639be6e2 00001f80
0x10a9ee30:   10aa0372 0054dc00 52ab76e8 10a9eebc
0x10a9ee40:   639bee1a 10a9ee70 10a9ef44 0000000a
0x10a9ee50:   52ab76e8 10aa9800 10a9ef54 00000000
0x10a9ee60:   0054dc00 0054dc00 0054dc00 00000004 

Instructions: (pc=0x00000000)
0xffffffe0:   


Register to memory mapping:

EAX=0x00100000 is an unknown value
EBX=0x52aada90 is an oop
{method} 
 - klass: {other class}
ECX=0x12aa0da0 is an oop
java.lang.Class 
 - klass: 'java/lang/Class'
EDX=0x00500001 is an unknown value
ESP=0x10a9edf0 is pointing into the stack for thread: 0x0054dc00
EBP=0x10a9ee18 is pointing into the stack for thread: 0x0054dc00
ESI=0x10a9edf4 is pointing into the stack for thread: 0x0054dc00
EDI=0x10a9ee1c is pointing into the stack for thread: 0x0054dc00


Stack: [0x010a0000,0x10aa0000],  sp=0x10a9edf0,  free space=255995k

---------------  P R O C E S S  ---------------

Java Threads: ( => current thread )
=>0x0054dc00 JavaThread "main" [_thread_in_Java, id=3628, stack(0x010a0000,0x10aa0000)]

Other Threads:
  0x56e40c00 VMThread [stack: 0x57060000,0x570b0000] [id=5364]

VM state:not at safepoint (normal execution)

VM Mutex/Monitor currently owned by a thread: None

Heap
 def new generation   total 157248K, used 2795K [0x12aa0000, 0x1d540000, 0x27ff0000)
  eden space 139776K,   2% used [0x12aa0000, 0x12d5ae88, 0x1b320000)
  from space 17472K,   0% used [0x1b320000, 0x1b320000, 0x1c430000)
  to   space 17472K,   0% used [0x1c430000, 0x1c430000, 0x1d540000)
 tenured generation   total 349568K, used 0K [0x27ff0000, 0x3d550000, 0x52aa0000)
   the space 349568K,   0% used [0x27ff0000, 0x27ff0000, 0x27ff0200, 0x3d550000)
 compacting perm gen  total 12288K, used 518K [0x52aa0000, 0x536a0000, 0x56aa0000)
   the space 12288K,   4% used [0x52aa0000, 0x52b21aa8, 0x52b21c00, 0x536a0000)
No shared spaces configured.

Card table byte_map: [0x56aa0000,0x56cd0000] byte_map_base: 0x56a0ab00

Polling page: 0x001c0000

Code Cache  [0x10aa0000, 0x10ae8000, 0x12aa0000)
 total_blobs=39 nmethods=0 adapters=18 free_code_cache=32499Kb largest_free_block=33278912

Compilation events (0 events):
No events

GC Heap History (0 events):
No events

Deoptimization events (0 events):
No events

Internal exceptions (0 events):
No events

Events (10 events):
Event: 0.015 loading class 0x00b0bd30 done
Event: 0.015 loading class 0x00b0bd10 done
Event: 0.015 loading class 0x00b16d50
Event: 0.015 loading class 0x00b16d50 done
Event: 0.015 loading class 0x00b13e28
Event: 0.015 loading class 0x00b13e28 done
Event: 0.015 loading class 0x00b1af98
Event: 0.015 loading class 0x00b1af98 done
Event: 0.015 loading class 0x00b1afc0
Event: 0.015 loading class 0x00b1afc0 done


Dynamic libraries:
0x002e0000 - 0x0030f000 	C:\Program Files\Integrity\IntegrityClient\jre\bin\java.exe
0x77090000 - 0x77210000 	C:\Windows\SysWOW64\ntdll.dll
0x754b0000 - 0x755c0000 	C:\Windows\syswow64\kernel32.dll
0x76c40000 - 0x76c87000 	C:\Windows\syswow64\KERNELBASE.dll
0x76710000 - 0x767b0000 	C:\Windows\syswow64\ADVAPI32.dll
0x76b90000 - 0x76c3c000 	C:\Windows\syswow64\msvcrt.dll
0x74f60000 - 0x74f79000 	C:\Windows\SysWOW64\sechost.dll
0x74c10000 - 0x74d00000 	C:\Windows\syswow64\RPCRT4.dll
0x74bb0000 - 0x74c10000 	C:\Windows\syswow64\SspiCli.dll
0x74ba0000 - 0x74bac000 	C:\Windows\syswow64\CRYPTBASE.dll
0x764c0000 - 0x765c0000 	C:\Windows\syswow64\USER32.dll
0x74d00000 - 0x74d90000 	C:\Windows\syswow64\GDI32.dll
0x765c0000 - 0x765ca000 	C:\Windows\syswow64\LPK.dll
0x75350000 - 0x753ed000 	C:\Windows\syswow64\USP10.dll
0x73300000 - 0x7349e000 	C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
0x75420000 - 0x75477000 	C:\Windows\syswow64\SHLWAPI.dll
0x74f00000 - 0x74f60000 	C:\Windows\system32\IMM32.DLL
0x75280000 - 0x7534c000 	C:\Windows\syswow64\MSCTF.dll
0x74880000 - 0x748c6000 	C:\PROGRA~2\Sophos\SOPHOS~1\SOPHOS~1.DLL
0x76230000 - 0x76235000 	C:\Windows\syswow64\PSAPI.DLL
0x65810000 - 0x658ce000 	C:\Program Files\Integrity\IntegrityClient\jre\bin\msvcr100.dll
0x63880000 - 0x63c00000 	C:\Program Files\Integrity\IntegrityClient\jre\bin\client\jvm.dll
0x6c600000 - 0x6c607000 	C:\Windows\system32\WSOCK32.dll
0x76b50000 - 0x76b85000 	C:\Windows\syswow64\WS2_32.dll
0x77060000 - 0x77066000 	C:\Windows\syswow64\NSI.dll
0x73500000 - 0x73532000 	C:\Windows\system32\WINMM.dll
0x6f8b0000 - 0x6f8bc000 	C:\Program Files\Integrity\IntegrityClient\jre\bin\verify.dll
0x6f890000 - 0x6f8b0000 	C:\Program Files\Integrity\IntegrityClient\jre\bin\java.dll
0x6f870000 - 0x6f883000 	C:\Program Files\Integrity\IntegrityClient\jre\bin\zip.dll
0x6c510000 - 0x6c5fb000 	C:\Windows\system32\dbghelp.dll

VM Arguments:
jvm_args: -Xss250M -Xms512M -Xmx1G 
java_command: C:\_projects\jenkins\run_and_log\MKS_connect_no_gui\mks_connect_test.jar C:/_projects/jenkins/DEV_m6.54.0.3/project.pj muell.txt
Launcher Type: SUN_STANDARD

我在任何论坛上寻找了两个星期的解决方案，但没有成功。我快要崩溃了-.-

有人知道问题出在哪里吗？

如果这是一个重要的方面，我忘了提到程序作为 jarfile 运行。

编辑:当我设置 -XX:PermSize100M -Xss250M -Xms512M -Xmx1G 时，出现以下异常:

com.mks.api.response.CommandException: mks.frame.app.ui.ViewException

这是什么意思？

Answer 1

这是操作系统检测到的 JVM 代码中的访问冲突。该应用程序可能会涉及，但您需要通过 PTC(现在拥有 MKS 产品套件的公司)支持提出这个问题。没有很多事情可以孤立地完成，因为这份报告看起来像许多其他不同的报告。如果 VM 中存在错误，那么任何数量的条件、环境和字节码都可能触发它。

如果您不能通过 PTC 解决这个问题，那么您可以尝试切换 JRE。 Source Integrity 使用自己安装到/jre 的私有(private) JRE(您可以在堆栈跟踪中看到这一点)，因此您可以轻松地将 JRE 的错误修复版本放在/jre 旁边，将旧版本重命名为/jre_old 并将新版本重命名为到/jre ，它应该选择新的。我认为这就是您需要做的所有事情，但我已经有很长时间没有使用该产品了。

这个不用说了，PTC等不支持，不过是个数据点。

现在，由于您拥有的数据点之一是仅当允许堆增长到某个大尺寸时才会触发，而且我知道大型沙箱会对堆施加相当大的压力，您甚至可以遇到硬件问题。也就是说，这可能就像一根坏内存棒一样简单。虽然现在这种情况很少见，但我以前见过，而且大多数时候我们很少像真正的 Java 应用程序那样使用内存资源。

此外，这似乎是一个 32 位 JVM，这意味着堆将非常受限。 Windows 上进程内存的分段方式，我们过去只能勉强将堆设置为超过 1Gb，这取决于必须共存于同一进程内存中的 native 库的大小、线程数和 permgen 空间.您可能刚刚达到进程内存限制。

完全披露:我曾经为 MKS 工作。