Bugs item #2963094, was opened at 2010-03-04 04:54 Message generated for change (Comment added) made by zmoelnig You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=2963094...
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pixes (pix_ objects) Group: None
Status: Pending Resolution: Fixed
Priority: 7 Private: No Submitted By: Hans-Christoph Steiner (eighthave) Assigned to: Nobody/Anonymous (nobody) Summary: gem crash with pix_video and pix_diff
Initial Comment: Using Pd-0.42.5-extended-20100224which included Gem 0.92.2 on Mac OS X/Intel 10.5.8 with a , I had a crash. In the attached patch, I disconnected the pix_film, then connected a [pix_video] and got a crash. I attached the Mac OS X crash dump too.
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig)
Date: 2010-03-05 20:14
Message: i think i fixed it with rev3151
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig) Date: 2010-03-05 19:33
Message: ay: it does crash when i manage to make the camera respond immediately (if i create a new camera object the initialization of the cam will take some frames, giving me a grace period that prohibits the crash)
----------------------------------------------------------------------
Comment By: IOhannes m zmlnig (zmoelnig) Date: 2010-03-05 19:31
Message: according to the log it is [pix_diff] that crashes.
could you provide detailed information about the colourspaces and dimensions (e.g. as reported by [pix_info] your sources (film/video) provide when the crash appears.
furthermore: does it happen if you send a [simd 0( message to [pix_diff] before you do anything?
(btw, here (debian eee) i could replace [pix_film] (with a movie 720x576/RGBA, switching to 640x480/YUV camera)
----------------------------------------------------------------------
You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=507079&aid=2963094...