Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

always crash after 34 slides..




Sorry, forgot to add crash-report and debugger-info. see at message end.



_______________________________________________
hoi list,

i'm experiencing a weird problem, and i hope someone can point me in a good direction.

i'm working on a slideshow application that uses quartz-compositions for the transitions.
i a later stage i'll probably wrap those .qtz-files inside plugins/ bundles, but for now i'm dynamically loading the files in a QCrenderer when they're needed.


this all works perfectly well, except for the fact that the app. always crashes when it shows the 34th image, and starts loading the 35th photo and the asociated transition-file.

it's always the 34th image/transition that it crashes on, regardless what images, transitions (playlist) it's rendering. so for instance a playlist containing only 3 images/transitions which is looping, will also crash whenever it starts the 35th transition.

i can't see the logic in this number 34. as far as i see it's got nothing to do with memory problems, since plenty RAM is available, and the app isn't leaking.

in what direction should i possibly look for an answer?
is there some underlying caching mechanism that gets stressed too much?
or other things i don't know about?
or is 34 actually the real answer to the question of life, universe and everything:?



thanks arri _______________________________________________


Thread 2 Crashed:
0 <<00000000>> 0xfffeff20 objc_msgSend_rtp + 32
1 com.apple.QuartzComposer 0x987a6d68 -[QCPatch(Private) _execute:arguments:] + 1076
2 com.apple.QuartzComposer 0x987a6754 -[QCPatch(Runtime) render:arguments:] + 288
3 com.apple.QuartzComposer 0x987e8d58 -[QCRenderer renderAtTime:arguments:] + 36
4 nl.com.test 0x0000b1f0 -[RenderLayer renderAtTime:arguments:] + 508
5 nl.com.test 0x00009d90 -[Sequencer renderAtTime:] + 188
6 nl.com.test 0x000045e4 -[RenderManager displayFrameForTime:] + 92
7 nl.com.test 0x00003d78 _displayLinkCallBack + 76
8 com.apple.QuartzCore 0x94296754 CVDisplayLink::performIO (CVTimeStamp*) + 296
9 com.apple.QuartzCore 0x94299a60 CVDisplayLink::runIOThread() + 756
10 libSystem.B.dylib 0x9002b508 _pthread_body + 96



and the debugger hangs on this line:

[renderer renderAtTime:renderTime arguments:nil];

..which has by then been called before succesfully 33 times.
renderer is a QCRenderer, which looks fine in the debugger.







_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.