Bug #155

Kinect Grabber does not work any more

Added by Christof Elbrechter over 11 years ago. Updated over 11 years ago.

Status:ClosedStart date:2013-02-21
Priority:HighDue date:
Assignee:Christof Elbrechter% Done:

100%

Category:-
Target version:icl-8.0

Description

The KinectGrabber' internal class KinectDevice gets stuck, in it's destructor. Unfortunately this
is always called at least once BEFORE the grabber provides any image.

History

#1 Updated by Christof Elbrechter over 11 years ago

  • Status changed from New to In Progress
  • Priority changed from Urgent to High
  • % Done changed from 0 to 50
  • hot-fix is available
  • we still need to find out where the actual issue is

#2 Updated by Viktor Richter over 11 years ago

  • Status changed from In Progress to Resolved
  • Assignee changed from Viktor Richter to Christof Elbrechter
  • % Done changed from 50 to 100

Bug resolved.

Seems like the main problem was that the run-loop of the FreenectContext-Thread was not properly locked.
After adding a lock, the device does not freze anymore.

I assume that otherwise the thread is stopped within 'freenect_process_events' making all further calls to freenect functions block.

#3 Updated by Christof Elbrechter over 11 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF