fix(macos): order windows out on exit to prevent KVO crash#820
Draft
fix(macos): order windows out on exit to prevent KVO crash#820
Conversation
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
On macOS, winit's event handler teardown triggers a display cycle flush that finds _NSTouchBarFinderObservation KVO observers on objects in an inconsistent state, causing a SIGILL crash via _crashOnException:. Fix: call [window orderOut:nil] on all windows as the first action in on_exit(), before returning control to eframe/winit. This lets AppKit properly tear down its display-related observations while the windows and their views are still alive. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ebf5e94 to
2a97da2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_NSTouchBarFinderObservationKVO observers on inconsistent objects[window orderOut:nil]on all windows as the first action inon_exit(), giving AppKit a chance to properly tear down display-related observations while windows and views are still aliveRoot cause
During shutdown, winit's event handler teardown triggers a display cycle flush (
CATransaction commit). This causes_NSTouchBarFinderObservation invalidateto remove KVO observers from objects that are already in an inconsistent state, throwing an NSException that AppKit catches and deliberately crashes on via_crashOnException:.Fix
By ordering all windows out before returning from
on_exit(), AppKit processes the window removal while everything is still alive and consistent — the KVO observers are properly detached during this orderly removal rather than during the chaotic winit teardown.Test plan
🤖 Co-authored by Claudius the Magnificent AI Agent