简体繁体 English

从32位切换到64位会导致Java上的跳跃运动侦听器退出

[英]Switching from 32-bit to 64 bit causes exit for a leap motion listener on java

原文 2015-08-07 23:03:28 4 1 java/ eclipse/ leap-motion

After taking a java program (with Eclipse IDE) to use leap motion listener from a 32-bit windows to a 64-bit windows, the program appears to be running properly. 使用Java程序（使用Eclipse IDE）从32位窗口到64位窗口使用跳跃运动侦听器后，该程序似乎运行正常。

The problem is that now the connection to the controller is initialized, connected then immediately exits without me doing anything. 问题在于，现在到控制器的连接已初始化，已连接，然后立即退出，而无需我做任何事情。

I tried putting my hand over the controller and got this error 我尝试将手放在控制器上，但出现此错误

A fatal error has been detected by the Java Runtime Environment: Java运行时环境检测到致命错误：

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000007fee8b4a975, pid=10516, >tid=23920 EXCEPTION_ACCESS_VIOLATION（0xc0000005）在pc = 0x000007fee8b4a975，pid = 10516，> tid = 23920

JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51->b16) Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows->amd64 compressed oops) Problematic frame: C [Leap.dll+0x2a975] JRE版本：Java（TM）SE运行时环境（8.0_51-b16）（内部版本1.8.0_51-> b16）Java VM：Java HotSpot（TM）64位服务器VM（25.51-b03混合模式窗口-> amd64压缩的oops ）问题框架：C [Leap.dll + 0x2a975]

Failed to write core dump. 无法写入核心转储。 Minidumps are not enabled by default on client >versions of Windows 默认情况下，在Windows客户端>版本上不启用小型转储

An error report file with more information is saved as: M:\\Leapduino\\Leapduino_test\\hs_err_pid10516.log 包含更多信息的错误报告文件被保存为：M：\\ Leapduino \\ Leapduino_test \\ hs_err_pid10516.log

If you would like to submit a bug report, please visit: http://bugreport.java.com/bugreport/crash.jsp The crash happened outside the Java Virtual Machine in native code. 如果您想提交错误报告，请访问： http : //bugreport.java.com/bugreport/crash.jsp该崩溃发生在Java虚拟机外部，以本机代码显示。 See problematic frame for where to report the bug. 请参阅有问题的框架以报告错误。