🤖 fix: skip splash screen on macOS dock reactivation #854
+2
−20
Conversation
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
ERR_FAILED (-2) loading splash.html from ASAR intermittently on macOS dock reactivation because: - macOS App Nap throttles idle apps - File descriptors to ASAR archive may be reclaimed after inactivity - The activate event fires before I/O is fully responsive Fix: Skip the splash screen on reactivation. Services are already loaded from initial launch, so window creation is fast (~100ms). The splash exists to cover heavy initialization—unnecessary on reactivation. _Generated with mux_
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
ERR_FAILED (-2)loadingsplash.htmlfrom ASAR intermittently on macOS dock reactivation because:activateevent fires before I/O is fully responsiveSolution
Skip the splash screen on reactivation. Services are already loaded from initial launch, so window creation is fast (~100ms). The splash exists to cover heavy initialization—unnecessary on reactivation.
-20 LoC, +2 LoC (net: -18)
Alternatives Considered
Generated with
mux