We saw the same issue starting with 10.10.3 and continuing through current 10.10.4 builds. Write up a radar and reference radar://problem/20368338 as a duplicate instance. -- Gary L. Wade (Sent from my iPhone) http://www.garywade.com/
> On May 28, 2015, at 11:34 AM, Matthew LeRoy <mle...@minitab.com> wrote: > > Hi, > > Anybody know anything about NSDocumentTitlebarPopoverViewController, and/or > why I’m getting application crashes due to a zombie’d instance thereof? > > Document-based app, Deployment Target and SDK both 10.8. Built using Xcode > 5.1.1 (5B1008) on Yosemite 10.10.3; running on the same system. Here’s what I > do: > > 1. Run my app. > 2. Open an existing document from disk. > 3. Click on the document name in the window’s titlebar to open the Document > name/tag/location popover. > 4. Wait a second or two. > 5. Click elsewhere in my document window to close the popover. > 6. Crash. > > Sometimes the crash happens immediately after the popover disappears; other > times it happens 1-3 seconds later. It doesn’t happen every time, but always > within two to three repetitions of steps 3–5. Here’s the stack trace when it > crashes: > > frame #0: 0x00007fff84a13d20 CoreFoundation`___forwarding___ + 768 > frame #1: 0x00007fff84a13998 CoreFoundation`__forwarding_prep_0___ + 120 > frame #2: 0x00007fff92603547 ViewBridge`-[NSRemoteViewBase > endAllModalSessions:] + 177 > frame #3: 0x00007fff925fbe74 ViewBridge`-[NSRemoteViewBase > viewWillMoveToWindow:] + 367 > frame #4: 0x00007fff864b90de AppKit`-[NSView _setWindow:] + 257 > frame #5: 0x00007fff849ea705 CoreFoundation`__53-[__NSArrayM > enumerateObjectsWithOptions:usingBlock:]_block_invoke + 133 > frame #6: 0x00007fff849e9e09 CoreFoundation`-[__NSArrayM > enumerateObjectsWithOptions:usingBlock:] + 313 > frame #7: 0x00007fff86c3d474 AppKit`__21-[NSView _setWindow:]_block_invoke735 > + 169 > frame #8: 0x00007fff864b9c54 AppKit`-[NSView _setWindow:] + 3191 > frame #9: 0x00007fff864c73d7 AppKit`-[NSVisualEffectView _setWindow:] + 214 > frame #10: 0x00007fff86722747 AppKit`-[NSPopoverFrame _setWindow:] + 111 > frame #11: 0x00007fff8670961f AppKit`-[NSWindow dealloc] + 1201 > frame #12: 0x00007fff8679c9f5 AppKit`-[_NSPopoverWindow dealloc] + 74 > frame #13: 0x00007fff864b68cc AppKit`-[NSWindow release] + 193 > frame #14: 0x00007fff8497fdb0 CoreFoundation`CFRelease + 304 > frame #15: 0x00007fff849a0bbd CoreFoundation`-[__NSArrayI dealloc] + 125 > frame #16: 0x00007fff9211d89c > libobjc.A.dylib`objc_object::sidetable_release(bool) + 236 > frame #17: 0x00007fff92103e8f libobjc.A.dylib`(anonymous > namespace)::AutoreleasePoolPage::pop(void*) + 575 > frame #18: 0x00007fff849a16f2 CoreFoundation`_CFAutoreleasePoolPop + 50 > frame #19: 0x00007fff8c1c1762 Foundation`-[NSAutoreleasePool drain] + 153 > frame #20: 0x00007fff8650ccc1 AppKit`-[NSApplication run] + 800 > frame #21: 0x00007fff86489354 AppKit`NSApplicationMain + 1832 > > After enabling Zombie Objects, I get the following in the console: > > 2015-05-28 14:19:58.291 MyApp[23684:2561441] *** > -[NSDocumentTitlebarPopoverViewController isKindOfClass:]: message sent to > deallocated instance 0x600000146f60 > > Google is no help, although it did uncover the following tweet from just a > few days ago: https://twitter.com/tonyarnold/status/603424801152086017. > > Anybody run across this before, or have any thoughts on what the problem > could be and/or how to debug? > > Thanks! > > Matt _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
