Yes, this is happening for me since 10.10. Origami has a fix for that, but that is 64bit only.
Cheers, Tamas > On 11 Feb 2016, at 20:16, George Toledo <gtole...@gmail.com> wrote: > > Has anyone noticed a problem with QC crashing in app close? > > At first, I noticed a relationship between that happening, and having opened > a composition that doesn't fully restore, because of not having a given > qcplugin or qcpatch loaded. > > I have closed out of QC without these crashes in El Cap, using a small subset > of QC stock patches, many times. > > However, I have also noticed some sort of edge case must be occurring where > QC can crash on app close, even without that. I have specifically tested the > very small amount of patches/plugins I have installed on a case by case > basis, and have concluded it is not because of custom plugins. I wonder if it > is just from interacting with the editor in some way, or maybe opening up > older compositions. > > This is what the related crashed thread info looks like: > > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 libobjc.A.dylib 0x00007fff86f544dd objc_msgSend + 29 > 1 com.apple.CoreFoundation 0x00007fff880b8da2 -[__NSArrayM > removeObjectAtIndex:] + 290 > 2 com.apple.Foundation 0x00007fff8ad0689e > postQueueNotifications + 824 > 3 com.apple.CoreFoundation 0x00007fff880c7e37 > __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 > 4 com.apple.CoreFoundation 0x00007fff880c7da7 > __CFRunLoopDoObservers + 391 > 5 com.apple.CoreFoundation 0x00007fff880b9a3a __CFRunLoopRun + 1178 > 6 com.apple.CoreFoundation 0x00007fff880b9338 CFRunLoopRunSpecific > + 296 > 7 com.apple.HIToolbox 0x00007fff9ad9e935 > RunCurrentEventLoopInMode + 235 > 8 com.apple.HIToolbox 0x00007fff9ad9e76f > ReceiveNextEventCommon + 432 > 9 com.apple.HIToolbox 0x00007fff9ad9e5af > _BlockUntilNextEventMatchingListInModeWithFilter + 71 > 10 com.apple.AppKit 0x00007fff8d9a60ee _DPSNextEvent + 1067 > 11 com.apple.AppKit 0x00007fff8dd72943 -[NSApplication > _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454 > 12 com.apple.AppKit 0x00007fff8d99bfc8 -[NSApplication run] > + 682 > 13 com.apple.QuartzComposer.editor 0x000000010986f262 0x10986d000 + 8802 > 14 com.apple.AppKit 0x00007fff8d91e520 NSApplicationMain + > 1176 > 15 libdyld.dylib 0x00007fff8f0d65ad start + 1 > > > -------- > > Is this a familiar issue? It's not really a big deal, because it doesn't > interfere with saves at all, but maybe it's worth filing a bug? > > Has anyone pegged down what is causing it, and if there is something that can > be avoided to keep it from happening? > > -George Toledo > _______________________________________________ > 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%40imimot.com > > This email sent to i...@imimot.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/archive%40mail-archive.com This email sent to arch...@mail-archive.com
