Reduce impact of org.gnome.SessionManager slow-down / freeze (issue 277) #282
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.
This provides a partial solution to #277
Previously: Using the org.gnome.SessionManager method repeatedly would
freeze system in 400-600 iterations.
Now:
Get to ~2000 iterations before system freezesEDIT: Get until 2000 iterations until mouse starts to feel laggy. It will finish even 10k iterations without freezing, but mouse is permanently laggy (until reboot).Contents
each time connection is closed (at least for now), as adding it helped
to get more iteration cycles.
warning ignore introduced in Fix: org.gnome.SessionManager RuntimeError (Issue 276) #278.