Hey, I can see similarities with your crash and few other threads on this mailing list. If I have understood correctly, the problem is with "Image with string" patch and certain graphics cards / drivers running on Mavericks.
Try searching for topic "QCImageManager crash, this time with HID Input device”. I’m testing your composition, no crash so far in 10 minutes. .aku -- Aku Meriläinen Mediasuunnittelija | Media Designer [email protected] +358 45 6500 865 On 20 Mar 2014, at 15:02, Dimitri Delcourt <[email protected]> wrote: > Hey Georges, > > Thanks for your reply. > > My QC library contains only my own macro patches, I have absolutely no plugin > installed. > > This is why I’m asking if the composition crashes on others’ machines as well. > If you could just launch this for a few minutes and see if it is stable on > your side? > >>>> dd_AngleDistance.qtz > > > Nice to hear from old-timers ;) > > d. > > > > > > > > > > On 20 Mar 2014, at 03:45, George Toledo <[email protected]> wrote: > >> I'd recommend trying out qc totally stock, with no third party addons, for >> awhile. Even if compositions you're working on don't involve plugins when >> you have the crashes. >> >> It may be that you still experience the crashes, but it may also get rid of >> them. >> >> The one thing, on my system at least, that I find can make qc crash is >> accessing two video patches at the same time, whether in the same or >> different compositions or apps. >> >> I wouldn't use OpenCL in any production scenario; even when you hit on >> something stable on your machine, gpu support differs greatly as does >> acceptable code for various OS versions. >> >> JavaScript can be OK, but I'd be wary of using a large amount of JavaScript >> patches simultaneously; it seems like it's possible to basically ask more >> than can be given, and spike the CPU into the app crashing. Which I guess >> isn't a surprise. >> >> Best regards, >> George Toledo >> >> On Mar 19, 2014, at 10:27 PM, Dimitri Delcourt <[email protected]> wrote: >> >>> All right, all right. >>> >>> So, I rebuilt the same file from scratch, and it didn’t crash while I was >>> editing it. Under Mavericks. >>> But did crash after saving the new file and reopening it later. >>> >>> I’ve come to the point where I don’t know what’s buggy and what’s not >>> anymore. >>> Closing a viewer window can make QC crash. >>> Quitting QC makes it crash. How’s that for a metaphor? >>> >>> Both files are doing fine under 10.6. >>> >>> Well. >>> >>> d. >>> >>> >>> >>> On 19 Mar 2014, at 03:02, Dimitri Delcourt <[email protected]> wrote: >>> >>>> Here’s another crash, and another log. >>>> Under Mavericks. >>>> >>>> File: dd_AngleDistance.qtz >>>> >>>> QC doesn’t crash at once, but after a while. >>>> Can anyone replicate? >>>> >>>> d. >>>> _______________________________ >>>> >>>> >>>> >>>> Process: Quartz Composer [513] >>>> Path: /Applications/Graphic Tools/Quartz >>>> Composer.app/Contents/MacOS/Quartz Composer >>>> Identifier: com.apple.QuartzComposer.editor >>>> Version: 4.6 (151) >>>> Build Info: QuartzComposerEditor-151000000000000~138 >>>> Code Type: X86-64 (Native) >>>> Parent Process: launchd [156] >>>> Responsible: Quartz Composer [513] >>>> User ID: 501 >>>> >>>> Date/Time: 2014-03-19 02:54:37.349 +0100 >>>> OS Version: Mac OS X 10.9.2 (13C64) >>>> Report Version: 11 >>>> Anonymous UUID: D96A22BC-E7D8-1CE3-A109-4BE840A6598A >>>> >>>> >>>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >>>> >>>> Exception Type: EXC_BAD_ACCESS (SIGBUS) >>>> Exception Codes: KERN_PROTECTION_FAILURE at 0x000000011494f000 >>>> >>>> VM Regions Near 0x11494f000: >>>> IOKit 0000000114947000-000000011494f000 [ 32K] >>>> rw-/rw- SM=ALI >>>> --> IOKit 000000011494f000-0000000114950000 [ 4K] >>>> r--/r-- SM=ALI >>>> IOKit 0000000114950000-0000000114971000 [ 132K] >>>> rw-/rw- SM=ALI >>>> >>>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >>>> 0 com.apple.IOAccelerator 0x00007fff9351ceee >>>> IOAccelContextAddResource + 23 >>>> 1 libGPUSupportMercury.dylib 0x00007fff89e0a4c7 gldObjectPurgeable + >>>> 837 >>>> 2 GLEngine 0x00007fff90f7bc64 gleObjectPurgeable + >>>> 853 >>>> 3 GLEngine 0x00007fff90ee1b54 >>>> glObjectPurgeableAPPLE_Exec + 191 >>>> 4 com.apple.QuartzComposer 0x00007fff8a1edf1d >>>> -[QCImageTextureBuffer setPurgeable:] + 676 >>>> 5 com.apple.QuartzComposer 0x00007fff8a1c3915 -[QCCache(Internal) >>>> _runGarbageCollectionForAge] + 636 >>>> 6 com.apple.QuartzComposer 0x00007fff8a1c82a3 -[QCCache(Private) >>>> _collectResourcesForAge] + 86 >>>> 7 com.apple.QuartzComposer 0x00007fff8a1c79e3 -[QCImageManager >>>> optimizeCaches] + 601 >>>> 8 com.apple.QuartzComposer 0x00007fff8a1c75fb -[QCImageManager >>>> reclaimResources] + 138 >>>> 9 com.apple.QuartzComposer 0x00007fff8a1d3a4c -[QCGraphicsContext >>>> renderPatch:time:arguments:] + 139 >>>> 10 com.apple.QuartzComposer 0x00007fff8a1d2bdc -[QCOpenGLContext >>>> renderPatch:time:arguments:] + 538 >>>> 11 com.apple.QuartzComposer 0x00007fff8a1d29ac -[QCPatch(Runtime) >>>> render:arguments:] + 76 >>>> 12 com.apple.QuartzComposer 0x00007fff8a2858b7 -[QCView >>>> renderAtTime:arguments:] + 76 >>>> 13 com.apple.QuartzComposer.editor 0x000000010f619597 0x10f60a000 >>>> + 62871 >>>> 14 com.apple.QuartzComposer 0x00007fff8a285b98 -[QCView >>>> render:arguments:] + 700 >>>> 15 com.apple.QuartzComposer 0x00007fff8a2856b2 -[QCView >>>> _renderTimer] + 375 >>>> 16 com.apple.QuartzComposer 0x00007fff8a259268 _TimerCallback + 82 >>>> 17 com.apple.CoreFoundation 0x00007fff8a851564 >>>> __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 >>>> 18 com.apple.CoreFoundation 0x00007fff8a85109f __CFRunLoopDoTimer + >>>> 1151 >>>> 19 com.apple.CoreFoundation 0x00007fff8a8c25aa __CFRunLoopDoTimers >>>> + 298 >>>> 20 com.apple.CoreFoundation 0x00007fff8a80c8e5 __CFRunLoopRun + 1525 >>>> 21 com.apple.CoreFoundation 0x00007fff8a80c0b5 CFRunLoopRunSpecific >>>> + 309 >>>> 22 com.apple.HIToolbox 0x00007fff9118ca0d >>>> RunCurrentEventLoopInMode + 226 >>>> 23 com.apple.HIToolbox 0x00007fff9118c7b7 >>>> ReceiveNextEventCommon + 479 >>>> 24 com.apple.HIToolbox 0x00007fff9118c5bc >>>> _BlockUntilNextEventMatchingListInModeWithFilter + 65 >>>> 25 com.apple.AppKit 0x00007fff935443de _DPSNextEvent + 1434 >>>> 26 com.apple.AppKit 0x00007fff93543a2b -[NSApplication >>>> nextEventMatchingMask:untilDate:inMode:dequeue:] + 122 >>>> 27 com.apple.AppKit 0x00007fff93537b2c -[NSApplication run] >>>> + 553 >>>> 28 com.apple.QuartzComposer.editor 0x000000010f60ce89 0x10f60a000 >>>> + 11913 >>>> 29 com.apple.AppKit 0x00007fff93522913 NSApplicationMain + >>>> 940 >>>> 30 libdyld.dylib 0x00007fff8db6d5fd start + 1 >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Quartzcomposer-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/quartzcomposer-dev/gtoledo3%40gmail.com >>> >>> This email sent to [email protected] > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Quartzcomposer-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/quartzcomposer-dev/aku.merilainen%40gmail.com > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [email protected]
