"Motion 2" memory leak with bitmaps ?
"Motion 2" memory leak with bitmaps ?
- Subject: "Motion 2" memory leak with bitmaps ?
- From: Christoph Vonrhein <email@hidden>
- Date: Mon, 16 Jul 2007 16:22:16 -0700
Hi,
In the -renderOutput: method I have this:
[getAPI getBitmap: &bitmapEmitter layerOffsetX: &imageBitmapOffset.x layerOffsetY: &imageBitmapOffset.y requestInfo: iInfoBitmap fromParm: bitmapEmitter_ParamID atTime: renderInfo.frame];
...and later this:
[bitmapEmitter release];
This works perfectly with Motion 3 for hours without a problem.
But with Motion 2.1.2 I can see a different behavior. I drop something into the image well, and let the plugin run. After a while (about 20-30 seconds on my MBP with 2 GB of RAM) Motion 2 slows down dramatically and I can hear the HD working heavily. When stop the playback, I can hear that OSX is working hard on the harddrive (memory swapping). The whole system gets very slow and all other already launched applications then take a long time to appear, when I click on them. I guess that the either the [bitmapEmitter release] does not really release the memory (why ??) or Motion 2.1.2 does something else in a strange way.
Any thoughts ?
Christoph
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden