What steps will reproduce the problem?
when i use the cvblob.Label in "real time" with kinect (with the depth data...)
the virtual memory never stop increasing,
i read thats already hapened
http://code.google.com/p/cvblob/issues/detail?id=5&can=1&q=memory
but it's write that the code was changed... do i have a old version , or do i
have to change something in the source or in my code...
i don't see in example something like cvblob.destructBlob...
of course when i use just kinect end cv lonely it doesn't happened
What version of the product are you using? On what operating system?
1. libfreeenect (last version of git)
2. python 2.7, opencv 2.3.1a,
Please provide any additional information below.
import freenect
import cv
import frame_convert
def show_depth():
my_depth, timestamp = freenect.sync_get_depth(0)
first_depth = 1024-my_depth
image = frame_convert.pretty_depth_cv(first_depth)
grey = image
cv.Threshold(grey, grey, 100, 255, cv.CV_THRESH_BINARY)
IPL_DEPTH_LABEL = 32
labelImg = cv.CreateImage(cv.GetSize(grey), IPL_DEPTH_LABEL, 1)
blobs = cvb.Blobs()
result = cvb.Label(grey,labelImg,blobs)
while 1:
show_depth()
and ... thanks the mysterious peoples that always answer to my asking
juju
Original issue reported on code.google.com by biogenem...@gmail.com on 7 Nov 2011 at 9:07
Original issue reported on code.google.com by
biogenem...@gmail.com
on 7 Nov 2011 at 9:07