a project i'm working uses 3 displaylink-threads, each rendering an
instance of the same qc-file in 3 different contexts, and this
results in a reproducible crash anywhere within about 30sec. after
starting the app. (on a macPro 4x2.66,10.4.9, QT 7.1.3 - 7.1.5)
today i've finally found that the crash doesn't happen when enabling
'Direct Core Image Rendering' on the Billboard-patch that renders the
final image.
the composition renders the image of a movie patch, through an
accumulator that is fead back it's own signal through a dissolve.
is this a bug or some compatibilty issue?
some additional/background -info;
• i didn't have this crash on a mac-mini (intel/1.66duo/10.4.9/
QT7.1.5) and a G5 (quad 2.5/10.4.9/QT 7.1.3).
after updateing Quicktimer on the G5 to 7.1.6 it also started
crashing there.
• when 'Enable Direct Core Image Rendering' is OFF, the frame-rate
reported by the FPS-display patch reports rates far beyond the 60 fps
one would expect considering the refresh-rate of the monitor (60Hz)
and the fact that the 'swap interval' of the context is set to 1.
when 'Enable Direct Core Image Rendering' is ON, the reported
framerate floats nicely around 60 as expected
• the backtrace always reports 'CGLSetPBuffer' as the bastard causing
the crash in the hanging thread.
• either cpu/gpu-speed or the number of cpu-cores has an influence,
since i don't have this crash on a mini with otherwise similair setup:
- cpu/gpu-speed because the mini is just not fast enough to reach the
high framerates as seen on the mac pro
- nr. of cores, because Quicktime seems to spawn more threads as
there are more cores available (depending on codec). this is just one
of the few noticable differences between setups... (but a wild guess)
additionally another question;
it took me ages to gather this, because all i had before, was the
crash-reports that users sent me.
the reports would never show this crash, since the main-thread of the
app. would usually still run very happily, just the 3 render-threads
would hang. the users would force-quit the app in order to start
using it again.
is there a way around this? and to have a sort of 'forced' crash report?
thanks,
arri
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
