Windows: Asus Xiton Pro driver crashes after 71 minutes about pcl

[rbrusu]

Thanks for the report Shaun. I believe the main difference between PointXYZRGBA and PointXYZ is that we're simply requesting OpenNI to hand us both RGB and Depth streams. Having an Xtion Pro as the data producer, also indicates that we're asking OpenNI to give us synchronized streams (if you would use a Kinect, the streams would not be in sync, as there's no synchronization enabled in firmware).

I'm thinking OpenNI 1.x is at fault here - and we could verify this by doing a very simple test with one of its basic NISimpleRead-based clients. If it is, this indicates the need to move to OpenNI2 internally.

[shaun-edwards]

Radu, I tried running tests with the NiViewer and NiSimpleRead. The NiSimpleRead did not exhibit the failure, although I assumed that was because it was not "subscribing" to multiple streams. I then tried, the NiViewer. It also continued to run long after the 71 minutes. I assume the NiViewer does use multiple feeds, although the image data does not display correctly. I'm not sure if this rules out the Ni driver, but it probably narrows the source of the problem.

[clantos]

Hello,
I also noticed the problem and solved it by re initializing the OpenNIGrabber when the callback stops. Is there any othe possible solutions?
Moreover, I tested Primesense Carmine 1.082 and Primesense Carmine 1.09 which both led to failure after 71 minutes, so probably is not a hardware issue.

[rbrusu]

So I think the only way to fix this properly is through the new OpenNI2 grabber.

[pauldol]

Hello,

I have a similar issue.
I am using 3 Xtion Pro cameras, Win7 32 bit. PCL 1.7 (manually built the dlls) and OpenNI 1.5.4.
I have three OpenNIGrabbers and I register to each of them a different callback.
Everything runs fine but roughly after an hour one of the callbacks stops working.

Yesterday I used the same framework with the new OpenNI2 grabber.
I used kwaegel's forked PCL repository version for the OpenNI2 grabber.
Again the same happened. Everything seemed to be working fine for an hour and then a callback stops working.

[pionex]

I'm still experiencing this problem with OpenNI2 as well. The grabber callback stops receiving frames after exactly 2^32 microseconds (71.5828 minutes). Although the callbacks have stopped, the program apparently keeps allocating memory for frames that don't appear to get deallocated and the program will quickly consume all of the memory in the computer.

Somewhere a 32-bit number must be overflowing and maybe causing a divide by zero. Are there any ideas on whether this is in the Xtion hardware, the asus driver, or OpenNI2?

[stale]

Marking this as stale due to 30 days of inactivity. It will be closed in 7 days if no further activity occurs.

[kunaltyagi]

The only common factor is either a core PCL code common to all grabbers or the hardware. The second looks more likely. Closing due to inactivity. Please reopen if you have different hardware and can test on them.