I guess it's getting a little off topic , but the ones that stand out in my
mind are both javascriptcore crashes, one with something starting with WTF, and
another with BADBEEF.
One issue I had pop up recently, in an app I wrote that can load qtz.'s, is
that if I have more than one Video patch loaded (in 10.8), it crashes. I've
heard report that this "just happens" in QuartzComposer now as well. I haven't
even looked at the crash report yet or even replicate, but it may be worth
mentioning.
May be something totally different, but it was a hard bug to track down at
first since it was only happening when two compositions were loaded that both
had the video patch. Often users link patches like Core Image directly to the
Video patch, so there may be some interplay going on in your case as well.
-gt
On May 18, 2013, at 3:30 AM, CoGe - Tamas Nagy <i...@cogevj.hu> wrote:
> Hey,
>
> thanks George, all of this make sense. The issue is related to Core Image,
> actually, have no idea what caused this, but, anyway, very cool method name :)
>
>
>
> 0 com.apple.CoreImage 0x91540295
> CoreImage_crashed_because_it_could_not_allocate_memory(void const*) + 17
>
> On May 18, 2013, at 9:25 AM, George Toledo <gtole...@gmail.com> wrote:
>
>> On second thought, the the bit about QCPatch(Private) doesn't necessarily
>> point to a private patch, it's just that _renderAtTime:arguments is listed
>> in the interface under QCPatch (Private). This is where methods for
>> execution mode, timebase, enabling/disabling, etc., happen.
>>
>> I think the com.apple.QuartzComposer points to a built in patch though.
>>
>> -gt
>>
>> On May 18, 2013, at 3:10 AM, George Toledo <gtole...@gmail.com> wrote:
>>
>>> Take this with a grain of salt, based on some stuff I've gleaned.
>>>
>>> The QCExporter likely has to deal with conversions between different image
>>> types behind the scenes. QCImage consists of many different image types,
>>> and there are various converters and exporters which QCImageManager handles.
>>>
>>> The other lines just have to do with the interface declarations for
>>> QCPatch; they just represent the methods that are called in the patch. I
>>> haven't thought it out too much, but on first glance it looks like it's
>>> probably referring to a consumer macro environment (because of
>>> executeSubatches…), that's maybe on external timebase(? the Customization
>>> execute:time:arguments), and it's probably also a private Apple macro patch
>>> happening in the composition. Not sure if that's actually where the crash
>>> is happening.
>>>
>>> On May 18, 2013, at 2:26 AM, CoGe - Tamas Nagy <i...@cogevj.hu> wrote:
>>>
>>>> Hi,
>>>>
>>>> last night I received a crash report from a user and it contains some
>>>> informations I never saw before.
>>>>
>>>> Before the crash, I see this error message in the console, anyone have any
>>>> ideas with is that QCExporter class? It's maybe just an internal stuff
>>>> which responsible for rendering CI patches inside QC?
>>>>
>>>> *** <QCExporter_CoreImage_Provider: 0x429490>: Failed creating texture
>>>> buffer from provider <QCPlugOutputImage = 0x421a80 | DOD = <QCRegion =
>>>> 0x4f4700 | rectangle = {{0, 0}, {1920, 1080}}> | colorspace = GenericRGB |
>>>> alpha = 1 | native pixel format = (null) | native target = (null) |
>>>> capabilities = 100 >
>>>>
>>>> From the crash report, this lines makes me curios, never saw them before:
>>>>
>>>> 63 com.apple.QuartzComposer 0x95214fe3 -[QCPatch(Extensions)
>>>> executeSubpatches:arguments:] + 65
>>>> 64 com.apple.QuartzComposer 0x95214f91 -[QCPatch(Customization)
>>>> execute:time:arguments:] + 61
>>>> 65 com.apple.QuartzComposer 0x95215d34 -[QCPatch(Private)
>>>> _renderAtTime:arguments:] + 132
>>>> 66 com.apple.QuartzComposer 0x9521cce4 -[QCContext
>>>> renderPatch:time:arguments:] + 846
>>>> 67 com.apple.QuartzComposer 0x9521c925 -[QCGraphicsContext
>>>> renderPatch:time:arguments:] + 92
>>>> 68 com.apple.QuartzComposer 0x9521b975 -[QCOpenGLContext
>>>> renderPatch:time:arguments:] + 557
>>>> 69 com.apple.QuartzComposer 0x9521b73e -[QCPatch(Runtime)
>>>> render:arguments:] + 78
>>>>
>>>> That "Private" thing makes me feel it was a Kineme plugin. Or maybe I am
>>>> wrong and its just an internal stuff in QC.
>>>>
>>>> Thanks for any ideas,
>>>>
>>>> Tamas
>>>> _______________________________________________
>>>> 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:
>>>> https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com
>>>>
>>>> This email sent to gtole...@gmail.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:
>> https://lists.apple.com/mailman/options/quartzcomposer-dev/info%40cogevj.hu
>>
>> This email sent to i...@cogevj.hu
>
> Tamas Nagy | Software Developer - CoGe VJ Software
> www.cogevj.hu | www.facebook.com/cogevj | www.twitter.com/lumabeamerz
>
>
>
>
>
>
>
>
>
_______________________________________________
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:
https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
