That's great. I'm not sure exactly "why" this happens, it shouldn't, but it used to happen in 10.5 as well. I'm pretty sure I rdar'd it, but another bug report couldn't hurt.
My thought is that the in this scenario, the qc evaluation mechanism can't tell that the RII that's upstream (and a subgraph that is a different comp) is programmed to give no values out that first call. It can't deliver a single frame yet, bc it's off to start. Since the render needs a value, and it thinks it should be getting one, stuff freezes up instead of rendering. It looks like it's totally confused about when/what is supposed to be rendering from the crash. I still think it's a bug. It may also be related to some stuff the RII does to keep things that it assumes aren't visible in the viewer from evaluating, from that "dod get bounding rect message" and the consumer graph part (or QCRender, whichever) can't get that to work right when it loads the RII oriented graph part. I'm unsure if that's the method that does that or not, so that's definitely conjecture, but I've had that RII feature cause me many headaches in the past, along with some added sl stuff that makes one have to do stuff like have a patch evaluating in the background in an rii to make feedback loops with an rii work right. The patch could use some love. Sent from my iPhone On Aug 31, 2011, at 12:55 PM, Tamas Nagy <tamas.lov.n...@gmail.com> wrote: > Yup, George, thanks, it did the trick, now works without crashes! > > On Aug 31, 2011, at 6:40 PM, George Toledo wrote: > >> Will it still crash if you disconnect the cable from "crosses" to each of >> the "Render" input on the Render In Image patches, so that the RII's are >> always on? >> >> On Wed, Aug 31, 2011 at 5:10 AM, Tamas Nagy <tamas.lov.n...@gmail.com> wrote: >> Hey, >> >> i made a little effect in QC which iterates Sprites. It works well in QC >> app, but when i trying to use in 3rd party QC capable apps (tested with my >> app CoGe, also with VDMX and Resolume Avenue), it recently crashes when i >> turn off Crosses and changing the Number of Crosses parameter ( which >> changing iterations count in QC). >> >> I have an MBP 13" with nVidia 320M. >> >> I'm not sure is a QC bug, or just missed some QC design patterns that cause >> the issue. >> >> Thanks! >> >> Tamas >> >> Thread 14 Crashed: >> 0 com.apple.QuartzComposer 0x936638a8 QCDodGetBoundingRect + 51 >> 1 com.apple.QuartzComposer 0x936396ef -[QCRenderingManager >> addPatch:context:time:arguments:nextExecutionTime:] + 1433 >> 2 com.apple.QuartzComposer 0x9363890b -[QCPatch(Private) >> __execute:arguments:] + 754 >> 3 com.apple.QuartzComposer 0x93662fd6 -[QCRenderingPatch >> __execute:arguments:] + 522 >> 4 com.apple.QuartzComposer 0x936385a6 -[QCPatch(Private) >> _execute:arguments:] + 1728 >> 5 com.apple.QuartzComposer 0x93638e98 -[QCPatch(Private) >> _executeSubpatches:arguments:] + 243 >> 6 com.apple.QuartzComposer 0x936af4bf -[QCIterator >> nextExecutionTimeForSubpatches:time:arguments:] + 176 >> 7 com.apple.QuartzComposer 0x93638bd5 -[QCPatch(Customization) >> nextExecutionTime:time:arguments:] + 81 >> 8 com.apple.QuartzComposer 0x93638b2f -[QCPatch(Private) >> _nextExecutionTime:arguments:] + 461 >> 9 com.apple.QuartzComposer 0x9363887b -[QCPatch(Private) >> __execute:arguments:] + 610 >> 10 com.apple.QuartzComposer 0x936385a6 -[QCPatch(Private) >> _execute:arguments:] + 1728 >> 11 com.apple.QuartzComposer 0x93638e98 -[QCPatch(Private) >> _executeSubpatches:arguments:] + 243 >> 12 com.apple.QuartzComposer 0x9369e988 -[QCRenderInImage >> _executeSubpatches:arguments:] + 3275 >> 13 com.apple.QuartzComposer 0x93638c99 -[QCPatch(Customization) >> nextExecutionTimeForSubpatches:time:arguments:] + 140 >> 14 com.apple.QuartzComposer 0x93638bd5 -[QCPatch(Customization) >> nextExecutionTime:time:arguments:] + 81 >> 15 com.apple.QuartzComposer 0x93638b2f -[QCPatch(Private) >> _nextExecutionTime:arguments:] + 461 >> 16 com.apple.QuartzComposer 0x9363887b -[QCPatch(Private) >> __execute:arguments:] + 610 >> 17 com.apple.QuartzComposer 0x936385a6 -[QCPatch(Private) >> _execute:arguments:] + 1728 >> 18 com.apple.QuartzComposer 0x9363907d -[QCPort >> _execute:arguments:] + 268 >> 19 com.apple.QuartzComposer 0x9363845a -[QCPatch(Private) >> _execute:arguments:] + 1396 >> 20 com.apple.QuartzComposer 0x9363907d -[QCPort >> _execute:arguments:] + 268 >> 21 com.apple.QuartzComposer 0x9363845a -[QCPatch(Private) >> _execute:arguments:] + 1396 >> 22 com.apple.QuartzComposer 0x9363907d -[QCPort >> _execute:arguments:] + 268 >> 23 com.apple.QuartzComposer 0x9363845a -[QCPatch(Private) >> _execute:arguments:] + 1396 >> 24 com.apple.QuartzComposer 0x93638e98 -[QCPatch(Private) >> _executeSubpatches:arguments:] + 243 >> 25 com.apple.QuartzComposer 0x93638ccd -[QCPatch(Customization) >> nextExecutionTimeForSubpatches:time:arguments:] + 192 >> 26 com.apple.QuartzComposer 0x93638bd5 -[QCPatch(Customization) >> nextExecutionTime:time:arguments:] + 81 >> 27 com.apple.QuartzComposer 0x93638b2f -[QCPatch(Private) >> _nextExecutionTime:arguments:] + 461 >> 28 com.apple.QuartzComposer 0x936388c3 -[QCPatch(Private) >> __execute:arguments:] + 682 >> 29 com.apple.QuartzComposer 0x936385a6 -[QCPatch(Private) >> _execute:arguments:] + 1728 >> 30 com.apple.QuartzComposer 0x93636ba5 -[QCContext >> nextExecutionTimeForPatch:time:arguments:] + 643 >> 31 com.apple.QuartzComposer 0x9363691c -[QCGraphicsContext >> nextExecutionTimeForPatch:time:arguments:] + 73 >> 32 com.apple.QuartzComposer 0x936366f3 -[QCOpenGLContext >> nextExecutionTimeForPatch:time:arguments:] + 552 >> 33 com.apple.QuartzComposer 0x93642863 -[QCContext >> renderPatch:time:arguments:] + 306 >> 34 com.apple.QuartzComposer 0x936426c2 -[QCGraphicsContext >> renderPatch:time:arguments:] + 96 >> 35 com.apple.QuartzComposer 0x93641670 -[QCOpenGLContext >> renderPatch:time:arguments:] + 614 >> 36 com.apple.QuartzComposer 0x93641402 -[QCPatch(Runtime) >> render:arguments:] + 92 >> >> >> >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com >> >> This email sent to gtole...@gmail.com >> >> >> >> >> -- >> George Toledo >> gtole...@gmail.com >> www.georgetoledo.com >> >> >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list (Quartzcomposer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com