Other than the memory location this is the sort of report that is generic and often as not occurs when QC asks for a resource that it can't find, like something on a file path, or an array of values or structure.
You are on 10.6.8, QC 4.0 and without a gander at the composition, there is little or nothing that can be gleaned beyond suggesting that you look at what values are not being satisfied [values here being any numeric, boolean, structure or URL].
If the lack of appropriate data feed isn't the issue, then it could be that the composition is asking the framework to do what your OS cannot currently do, whatever that is. Again having to guess here. It might be a problem with a plugin that loads as a valid patch or plugin, but which asks of QC and it's supporting frameworks something that creates a failure mid flight, or even mid pre flight [at loading time of Viewer window I mean].
Quartz Composer Crashes - what a headline •~, :-).
So what's new? Nothing much, I'm afraid.
Other than the memory location this is the sort of report that is generic and often as not occurs when QC asks for a resource that it can't find, like something on a file path, or an array of values or structure.
You are on 10.6.8, QC 4.0 and without a gander at the composition, there is little or nothing that can be gleaned beyond suggesting that you look at what values are not being satisfied [values here being any numeric, boolean, structure or URL].
If the lack of appropriate data feed isn't the issue, then it could be that the composition is asking the framework to do what your OS cannot currently do, whatever that is. Again having to guess here. It might be a problem with a plugin that loads as a valid patch or plugin, but which asks of QC and it's supporting frameworks something that creates a failure mid flight, or even mid pre flight [at loading time of Viewer window I mean].