Simple-OpenNI 用于使用 Kinect 处理致命错误
整个夏天我都在使用 SimpleOpenNI，一个用于处理的包装器。我用它在 Kinect 上制作游戏和演示。上周，我在处理窗口中遇到了致命错误，并且所有 SimpleOpenNI 项目都无法工作。错误如下：
SimpleOpenNI Version 0.20
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x72e8f955, pid=4596, tid=4624
JRE version: 6.0_24-b07
Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 )
Problematic frame:
C [OpenNI.dll+0xf955]
An error report file with more information is saved as:
C:\Users\mss042\Desktop\processing-1.5.1\hs_err_pid4596.log
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.
似乎新的 OpenNI/NITE/SensorKinect 驱动程序无法与 SimpleOpenNI 包装器一起使用。我已经与使用旧驱动程序的人尝试过，一切仍然有效。问题是，您无法从网站下载旧驱动程序，因此我无法测试是否是这样。您可以看到我从 simpleopenni 网站下载的所有内容：http://code.google.com /p/simple-openni/
任何有关此错误的帮助将不胜感激。谢谢。
麦克风
I have been using SimpleOpenNI, a wrapper for Processing, all summer now. I use it for the Kinect to make games and demos. Last week, I have been getting a fatal error in my processing window and none of the SimpleOpenNI projects will work. Here is the error:
SimpleOpenNI Version 0.20
A fatal error has been detected by the Java Runtime Environment:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x72e8f955, pid=4596, tid=4624
JRE version: 6.0_24-b07
Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 )
Problematic frame:
C [OpenNI.dll+0xf955]
An error report file with more information is saved as:
C:\Users\mss042\Desktop\processing-1.5.1\hs_err_pid4596.log
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.
It appears as if the new OpenNI/NITE/SensorKinect drivers do not work with the SimpleOpenNI wrapper. I have tried it with people using the old drivers and everything still works. Problem is, you cannot download the old drivers off of the websites so I cannot test if it's that or not. You can see everything I've downloaded from the simpleopenni site: http://code.google.com/p/simple-openni/
Any help with this error would be appreciated. Thanks.
Mike
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
OpenNI.dll 似乎有问题。确保：
在大学有一个 Kinect 研讨会，我使用 Windows 的同事都遇到了驱动程序问题，
所以我只是传递他们所做的事情：
即使他们有 64 位版本的 Windows，他们也使用 32 位版本，并使用 Brekel OpenNI Kinect 自动安装程序 - 开发版 v1.3.2.3.exe（通过 developkinect 直接链接。 com）阅读此消息后：
对Issue#17 在 SimpleOpenNI 项目问题页面上。
另一位同事在处理中使用了 Synapse 和 OSC 而不是 SimpleOpenNI，但她有驱动程序存在大量错误（基本上花了几个小时卸载/安装不同版本）。就她而言，从计算机中卸载任何以前的部分或完整驱动程序并删除与 PrimeSense（Sensor、Nite）和 OpenNI 相关的任何注册表项，然后使用 Synapse 页面上的链接中的安装程序，对她来说很有效。
华泰
It looks like there's a problem with OpenNI.dll. Make sure that:
Had a Kinect Workshop in Uni, and my colleagues using Windows all had issues with the drivers,
so I'm just passing on what they did:
Even though they had 64-bit versions of Windows they used the 32-bit version, and used Brekel OpenNI Kinect Auto Installer - Developer Edition v1.3.2.3.exe(direct link via developkinect.com) after reading this message:
in Issue#17 on the SimpleOpenNI project issues page.
Another colleague used Synapse and OSC in Processing instead of SimpleOpenNI, but she had loads of errors with the drivers (basically spent a few good hours uninstalling/installing different versions). In her case, uninstalling any previous partial or complete drivers from the machine and deleting any registry entries related to PrimeSense(Sensor, Nite) and OpenNI, then using the installers from the links on the Synapse page, worked for her.
HTH
这个可能性不大，但如果 Kinect USB 和/或电源被拔掉，也会给出确切的错误。认为值得一提的是，因为从错误消息本身来看并不明显，如果有人踢掉电源并开始搜索上述异常，它可能会对他们有所帮助:)
This is a long shot, but that exact error is also given if the Kinect USB and/or power supply simply becomes unplugged. Thought it was worth mentioning as it is not obvious from the error message itself and it may help someone out if they kicked their power supply and started searching for the above exception :)