App crashes with objc_msgSend() selector name: retain in [_NSCGSWindowBuffer colorSpace]

A number of my users are reporting crashes of my app on macOS Sierra 10.12 (16A323).


All crashes seem to be caused by a call to “retain” on [_NSCGSWindowBuffer colorSpace].


Did anybody else run into this? This seems to be a specific problem on macOS Sierra. I've not recieved any crash reports like these for previous versions.


Full stack trace below:


Date/Time: 2016-10-20 10:20:21.913 -0700

OS Version: Mac OS X 10.12 (16A323)

Report Version: 12

Anonymous UUID: D57CA51A-EB79-F254-AAD5-1B93D2E1C67E


Sleep/Wake UUID: 24C32766-9490-4013-9620-10936FE9E4AD


Time Awake Since Boot: 28000 seconds

Time Since Wake: 120 seconds


System Integrity Protection: enabled


Crashed Thread: 0 Dispatch queue: com.apple.main-thread


Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00001ffa962cbec0

Exception Note: EXC_CORPSE_NOTIFY


Termination Signal: Segmentation fault: 11

Termination Reason: Namespace SIGNAL, Code 0xb

Terminating Process: exc handler [0]


VM Regions Near 0x1ffa962cbec0:

CoreAnimation 0000000117b7f000-0000000118940000 [ 13.8M] rw-/rwx SM=PRV

-->

JS JIT generated code 000025ad5e800000-000025ad5e801000 [ 4K] ---/rwx SM=NUL


Application Specific Information:

objc_msgSend() selector name: retain



Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libobjc.A.dylib 0x00007fffd9b86b5d objc_msgSend + 29

1 com.apple.AppKit 0x00007fffc3274a35 -[_NSCGSWindowBuffer colorSpace] + 33

2 com.apple.AppKit 0x00007fffc3248d11 __NSCGSWindowBackingStoreMark__block_invoke + 997

3 com.apple.AppKit 0x00007fffc320c4ec NSCGSTransactionRunPreCommitActionsForOrder_ + 289

4 com.apple.AppKit 0x00007fffc320c3b8 NSCGSTransactionRunPreCommitActions_ + 31

5 com.apple.AppKit 0x00007fffc320c38d __39+[_NSCGSTransaction currentTransaction]_block_invoke + 34

6 com.apple.QuartzCore 0x00007fffcaf4da4a CA::Transaction::run_commit_handlers(CATransactionPhase) + 46

7 com.apple.QuartzCore 0x00007fffcb05558f CA::Context::commit_transaction(CA::Transaction*) + 959

8 com.apple.QuartzCore 0x00007fffcaf4c5e5 CA::Transaction::commit() + 475

9 com.apple.AppKit 0x00007fffc34ee1cd __37+[NSDisplayCycle currentDisplayCycle]_block_invoke.31 + 323

10 com.apple.CoreFoundation 0x00007fffc5451f67 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23

11 com.apple.CoreFoundation 0x00007fffc5451ed7 __CFRunLoopDoObservers + 391

12 com.apple.CoreFoundation 0x00007fffc5432b79 __CFRunLoopRun + 873

13 com.apple.CoreFoundation 0x00007fffc54325b4 CFRunLoopRunSpecific + 420

14 com.apple.HIToolbox 0x00007fffc49d3f6c RunCurrentEventLoopInMode + 240

15 com.apple.HIToolbox 0x00007fffc49d3da1 ReceiveNextEventCommon + 432

16 com.apple.HIToolbox 0x00007fffc49d3bd6 _BlockUntilNextEventMatchingListInModeWithFilter + 71

17 com.apple.AppKit 0x00007fffc30ca5f5 _DPSNextEvent + 1093

18 com.apple.AppKit 0x00007fffc37da8eb -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637

19 com.apple.AppKit 0x00007fffc30befbd -[NSApplication run] + 926

20 com.apple.AppKit 0x00007fffc3089a8a NSApplicationMain + 1237

21 libdyld.dylib 0x00007fffda472255 start + 1

Replies

For refernce, more people are running into this. The discussion moved to:


https://forums.developer.apple.com/message/192843#192843