jdeboi / simple-openni

Automatically exported from code.google.com/p/simple-openni
0 stars 0 forks source link

EXCEPTION_ACCESS_VIOLATION OpenNI.dll+0x10345 #22

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
I've got a problem... I installed:
-PrimaSense Package Stable for Windows x86 20.3.3.6 dev edition
-SensorKinect-Win-OpenSource32 5.0.5.1
-JDK 7u1 x86
-Processing 1.5.1 without Java
-Eclipse x86
-SimpleOpenNI-0.20-win32
-Windows 7 x64

And when I run this program:

import processing.core.*;
import SimpleOpenNI.*;

public class T2Go extends PApplet{

     SimpleOpenNI  context;

      public void setup() {
        context = new SimpleOpenNI(this);
        context.enableDepth();
      }

      public void draw() {
      } 
}

I get error (full log in attached file), what's more, there is no problem when 
I delete context.enableDepth(); so I think the library was linked correctly. 
Same error with processing and eclipse.

I tried to install everything in x64 version but I can't pass 
java.lang.UnsatisfiedLinkError: no SimpleOpenNI so I gave up — with x86 I 
don't have this problem. 

I uninstalled freenect drivers and I can see in device manager under PrimaSense 
3 kinect devices so I hope it's ok. 

Do you have any idea?

Log's heder:

# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6ce90345, pid=4304, tid=5024
#
# JRE version: 7.0_01-b08
# Java VM: Java HotSpot(TM) Client VM (21.1-b02 mixed mode windows-x86 )
# Problematic frame:
# C  [OpenNI.dll+0x10345]
#
# Failed to write core dump. Minidumps are not enabled by default on client 
versions of Windows

Original issue reported on code.google.com by ess....@gmail.com on 7 Dec 2011 at 8:54

Attachments:

GoogleCodeExporter commented 8 years ago
the same error with windows vista x86 and
-PrimaSense Package Stable for Windows x86 20.3.3.6 dev edition
-SensorKinect-Win-OpenSource32 5.0.5.1
-Processing 1.5.1 with Java
-SimpleOpenNI-0.20-win32

I think there is something wrong w

Original comment by ess....@gmail.com on 13 Dec 2011 at 3:49

GoogleCodeExporter commented 8 years ago
Should be fixed with version 0.24+

Original comment by m...@paus.ch on 4 Jan 2012 at 4:08