so far, i know that when the crash occurs, the memory for the
QCRenderer-object is actually already freed somehow before i
release it myself. i suspected this already, because before i
didn't have this problem but had a huge memory leak instead because
i didn't release propertly.
i have no idea why/where/by-whom it is being freed (and why it is
always the 34th slide where it goes wrong).
in this case, each slide (image) is accompanied by a transition (QC
composition). so for each image i also load a new QCRenderer with
matching QC composition.
i've tried using the same composition for each slide, but that also
crashes when loading the 34th slide, no matter which composition i
use.
is it bad practice to dynamically load/unload composition like this?
should i take special care with retaining/releasing QCRenderers?
We have a know issue in 10.4.7 (or 10.4.6 and later - I don't
remember exactly) where deallocating a QCRenderer crashes. I'm pretty
sure that's what you're hitting.
We are working on fixing that in the next software update
________________________________________________________
Pierre-Olivier Latour email@hidden
Quartz Composer Team Apple Computer, Inc.
