fix(Workspace): wrong assumption caused WM to SEGV when a focused window was being unmanaged by the WM and there's not any other window to focus #513
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.
If
wasFocused
istrue
, the value ofnew_focused_window
shouldn't be NULL, but in a specific scenario, it is, and the window manager just SEGV. I triggered this SIGSEGV myself while using NEXTSPACE. Debian 12 under Bedrock Linux (no influence of other distros, only Debian packages & build tools).The flow of:
doesn't set
wasFocused
tofalse
, butnew_focused_window
is NULL, and this code flow segfaults the entire WM.Crash: