On Feb 26, 2007, at 07:29 42, Pierre-Olivier Latour wrote:
I don't see anything special in the crash log. Can you try with a
different composition for the slideshow, like a very very simple
one? Also try running with various malloc options like
MallocScribble, MallocGuardEdges... to detect potential memory
corruption - see man malloc for help
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?
