search

heuermh / leap-motion-processing

Leap Motion library for Processing
GNU General Public License v3.0
122 stars 31 forks source link

NullPointerException: null upcall object; Invalid Memory Access #4

Closed Glchriste closed 11 years ago

Glchriste commented 11 years ago

When you set size(1280, 72) in setup() rather than size(16_50, 9_50) and run, the program immediately exits. Sometimes it quits with a memory error. Example:

"Exception in thread "Thread-4" java.lang.NullPointerException: null upcall object Invalid memory access of location 0xf001816e eip=0x31d848ec"

heuermh commented 11 years ago

Thanks for submitting this issue.

I am not able to reproduce your first issue with size(1280, 72) on any of Processing versions 1.5.1, 2.0b6, or 2.0b7 on OSX. What version of Processing are you using and on what platform(s)?

The second issue ("null upcall object") was reported in issue #2. As I said in that issue, I should be able to work on a fix as soon as my hardware arrives (tomorrow, hopefully).

Glchriste commented 11 years ago

That's interesting. It's 2.0b7 on OSX Mountain Lion. Could you contact me at glchriste@gmail.com? I would like to send you the exact code for you to test on your machine. I added some code to it that determines the screen pixels (relative to the app window frame) based on where the user is pointing at the screen. That code works fine with the size given in your example. When the size changes to anything larger, the problem occurs.

Glchriste commented 11 years ago

Also, I made a typo. I meant 720 rather than 72.

Glchriste commented 11 years ago

In addition, when I try to run working code in Processing 1.5.1, I get the error: "The import java.awt.Frame collides with another import statement. This probably qualifies as a separate issue if others run into the same error without dealing with this one.

heuermh commented 11 years ago

Duplicate of #2