NSInternalInconsistencyException assertion from [NSRemoteView containingWindowWillOrderOnScreen:] on macOS 27 (26A5378j)

UI Frameworks AppKit
gotow OP
Created 1w
Replies 4
Boosts 2
Views 148
Participants 4

Is anyone else getting these assertion crashes on developer beta 3 of Golden Gate? I've gotten more than a dozen crash logs from users running macOS 27 (26A5378j) that all look like this:

assertion failed: '<NSRemoteView: 0x79cb366700 com.apple.SafariPlatformSupport.Helper SPCompletionListServiceViewController> notified of <NSStatusBarWindow: 0x79cbef7480> but expected (null)' in -[NSRemoteView containingWindowWillOrderOnScreen:] on line 4221 of file /AppleInternal/Library/BuildRoots/4~CSuOugB1YCxzYMPRWEumvvfCTNtf98eItTmsbJU/Library/Caches/com.apple.xbs/TemporaryDirectory.N8fh9t/Sources/ViewBridge/NSRemoteView.m

but with various windows from my app after "notified of".

They're getting thrown when one of my windows is made frontmost, either using NSWindow.orderFrontRegardless or NSWindow.makeKeyAndOrderFront, or (in the case above) when my status item is shown. It's intermittent - I've been unable to reproduce it so far - but definitely happening repeatedly based on my Sentry crash logging.

Is this a bug in Golden Gate b3, or am I doing something to provoke this? I've submitted it via Feedback Assistant (FB23642313).

Thanks

  • Jon

P.S. Full stack trace attached for the exception thrown when the assertion fails for NSStatusBarWindow

NSInternalInconsistencyException stack trace.txt
Answered by DTS Engineer in 897814022

Thank you for reporting.

I am relating your reports and making sure they are routed to the correct engineering team. Updates will be provided to you through Feedback Assistant. There, you can track if the report is still being investigated, has a potential identified fix, or has been resolved in another way.

For more details on Feedback Status, please see “Understanding the Status of Your Feedback” linked here: https://developer.apple.com/bug-reporting/status

When we receive multiple reports, it helps us understand the impact of an issue which can drive priority, so thank you.

 Travis

Replies  4
Boosts  2
Views  148
Participants  4
pawelmtw OP
1w

We're seeing this error as well. In our case, it occurs when a child NSWindow contains an editable text field: closing that window and opening a new one triggers the crash. We've found that removing the editable text field prevents the crash, but this is clearly a bug in Golden Gate Beta 3...
maxik OP
3h

I experience the same crash in my app on macOS 27 beta. It happens when I call NSAlert.beginSheetModalForWindow

My stack trace:

Application Specific Backtrace 0:
0   CoreFoundation                      0x000000018bb76448 __exceptionPreprocess + 176
1   libobjc.A.dylib                     0x000000018b5d45e4 objc_exception_throw + 88
2   CoreFoundation                      0x000000018bb9af50 _CFBundleGetValueForInfoKey + 0
3   ViewBridge                          0x00000001966063f0 -[NSRemoteView containingWindowWillOrderOnScreen:] + 216
4   CoreFoundation                      0x000000018bafafc4 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148
5   CoreFoundation                      0x000000018bb89e88 ___CFXRegistrationPost_block_invoke + 92
6   CoreFoundation                      0x000000018bb89dcc _CFXRegistrationPost + 440
7   CoreFoundation                      0x000000018bac7300 _CFXNotificationPost + 688
8   Foundation                          0x000000018d1ad384 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
9   AppKit                              0x000000019005c970 -[NSWindow _doWindowWillBeVisibleAsSheet:] + 28
10  AppKit                              0x0000000190994ad0 -[NSWindow _reallyDoOrderWindowAboveOrBelow:] + 1104
11  AppKit                              0x0000000190995698 -[NSWindow _reallyDoOrderWindow:] + 64
12  AppKit                              0x000000019099591c -[NSWindow _doOrderWindow:] + 300
13  AppKit                              0x000000019018de4c -[NSApplication _orderFrontModalWindow:relativeToWindow:] + 268
14  AppKit                              0x00000001901cc984 -[NSWindow _beginWindowBlockingModalSessionForSheet:service:completionHandler:isCritical:] + 1016
15  AppKit                              0x000000019020db2c __54-[NSAlert beginSheetModalForWindow:completionHandler:]_block_invoke + 280
16  AppKit                              0x000000019020ab90 -[NSAlert beginSheetModalForWindow:completionHandler:] + 116

I've also submitted it: FB23794308
gotow OP
3h

My feedback has been updated with "Potential fix identified - For a future OS update", so I'm hopeful we'll see a fix in the next beta release.

DTS Engineer OP
Apple
3h
Accepted Answer

Thank you for reporting.

I am relating your reports and making sure they are routed to the correct engineering team. Updates will be provided to you through Feedback Assistant. There, you can track if the report is still being investigated, has a potential identified fix, or has been resolved in another way.

For more details on Feedback Status, please see “Understanding the Status of Your Feedback” linked here: https://developer.apple.com/bug-reporting/status

When we receive multiple reports, it helps us understand the impact of an issue which can drive priority, so thank you.

 Travis

NSInternalInconsistencyException assertion from [NSRemoteView containingWindowWillOrderOnScreen:] on macOS 27 (26A5378j)
First post date Last post date
 
 
Q