hi pol,
attached you'll find the crashlog.
i hope the problem has an obvious solution.
i'm using a workaround right now where i initiate all QCrenderers
when the application loads,
and just re-use them rather than disposing/reloading..
this is stable, but it has two major dissadvantages;
it has a huge memory footprint. it uses between 150 and 300 Mb,
whereas my initial app. would sometimes peeks at 50Mb..but mostly
sit on ± 30Mb.
the other problem is that all the renderers have to be re-
initialised when the glContext changes
(for instances going to fullscreen) which takes a lot of time.
so i would really appreciate it if there's a fix!
thanks for wasting your sundays' rest on the problems of a
stranger.. :)
gr
arri
On Feb 25, 2007, at 18:47 37, Pierre-Olivier Latour wrote:
Can you send the entire crash report?
On Feb 25, 2007, at 1:14 AM, arri wrote:
On Feb 25, 2007, at 03:37 14, Troy Koelling wrote:
I see that the thread that crashed is thread 2, are you using
multiple threads to render the slideshow? QCRenderer is not
thread safe, meaning it can be used on arbitrary threads but you
cannot access the same instance of the renderer simultaneously.
You may be doing it right, but my suspicions were raised when I
saw which thread crashed.
thread 2 is the displaylink callback thread. the QCRenderers are
created/disposed on that thread, and not accessed from outside.
but i understand you suspicion..
<PlacidCrashLog.tgz>
