Fix crash and synchronize gui when disabling gi
with active debug visualization mode (backport #3062)
#3066
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.
🦟 Bug fix
Fixes #3060
Summary
When
gi
is being disabled (Enabled
changes fromtrue
tofalse
), the code sets the debug visualization mode toNone
, marks it as dirty, and sets a flag. After releasing the mutex lock, if theflag
is set, it emits theDebugVisualizationModeChanged
signal to notify the GUI to update.This ensures internal state consistency and prevents crashes by forcing the debug visualization mode to
None
whengi
is off. Emitting the signal outside the lock avoids deadlocks and keeps the GUI synchronized with the internal state.Checklist
codecheck
passed (See contributing)This is an automatic backport of pull request Fix crash and synchronize gui when disabling
gi
with active debug visualization mode #3062 done by Mergify.