What steps will reproduce the problem? 1.As soon as user's skeleton starts getting tracked,within few seconds a dialog box pops out depicting the above said issue.(attached as an image) 2.No problem until there is anyone under the field of view of kinect. 3. After closing the dialog box,the program runs normally.

What is the expected output? What do you see instead? The processing window appears with depth image from kinect and shows it perfectly. The program should run normally without popping out any error.But instead of that a dialog box appears saying "Primesense OpenNI module has stopped working" and hence I have to manually go and close it for further running the code. After closing that dialog box, everything worls normally

What version of the product are you using? On what operating system? I am using win7 64 bit OS with all 64bit drivers from primesense installed.

Please provide any additional information below. I don't know why I am getting this issue, and it is sometimes frustrating to close the popped out error whnever i try to run my code..

I am really new to this issue.. Anybody have any idea, how to get rid of this problem...??

Hello everyone,

I have exactly the same problem.

My processing program is using the depth map data. After some launch, I have the "Primesense OpenNI module has stopped working" error message. If I "close the program", everything works fine. Sometimes, this message only show when I close the processing window.

I am also on Win7 64 bits OS and OpenNI Drivers.

And for me, this is also the XnVSceneServer64_1_5_2.exe that crash.

If anyone have an idea how to handle this probleM.

Hi,well at the end I couldn't figure out its cause nor I found the solution. But I used a better approach. I added robot mouse class and programmed it forcefully to click on the area where "close the Program" on the dialog box appears... After this, the dialog box exits as soon as it appears.... :-) Remember,to close the processing window you cannot control the physical mouse then. For then you could either use "Alt+F4" or add a keyboard event..:)

+1 for same issue. Same setup - Win7 64bit.

I have the same issue. Currently running Processing 1.5.1 + SimpleOpenNi 0.27 on a windows 8 64 bit machine.

+1

Same setup same issue

(however, I think in my case it has to do with the context being passed to another class where it inits a couple of things)