-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.x] Resolve issue where the Godot app remains stuck when resuming. #51584
Merged
akien-mga
merged 1 commit into
godotengine:3.x
from
m4gr3d:investigate_godot_resume_stalls_3_x
Aug 13, 2021
Merged
[3.x] Resolve issue where the Godot app remains stuck when resuming. #51584
akien-mga
merged 1 commit into
godotengine:3.x
from
m4gr3d:investigate_godot_resume_stalls_3_x
Aug 13, 2021
Conversation
This file contains 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
Nice, that explains the weird bahaviour. Thanks for the fix! I tested it with my project via the "Don't keep activities" debug option and by opening a lot other other apps until i could see it getting killed by the system in the logs. Works great! |
Is this fix also needed in |
m4gr3d
changed the title
Resolve issue where the Godot app remains stuck when resuming.
[3.x] Resolve issue where the Godot app remains stuck when resuming.
Aug 12, 2021
m4gr3d
force-pushed
the
investigate_godot_resume_stalls_3_x
branch
from
August 12, 2021 19:57
4be6ef2
to
8f6fe5f
Compare
akien-mga
approved these changes
Aug 12, 2021
This was caused by the fact that a new instance of Godot was created at resume while a previous instance already existed. The previous instance would then go through its cleanup lifecycle, and would thus attempt to close the entire app, leading to the system to restart the app, thus starting the cycle anew. The fix involves reusing the previous instance of Godot if one is available instead of creating a new one, as well as giving control to the host activity for how the process should be terminated.
m4gr3d
force-pushed
the
investigate_godot_resume_stalls_3_x
branch
from
August 13, 2021 03:58
8f6fe5f
to
874aa17
Compare
Thanks! |
Cherry-picked for 3.3.3. |
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.
This was caused by the fact that a new instance of Godot was created at resume while a previous instance already existed.
The previous instance would then go through its cleanup lifecycle, and would thus attempt to close the entire app, leading to the system to restart the app, thus starting the cycle anew.
The fix involves reusing the previous instance of Godot if one is available instead of creating a new one, as well as giving control to the host activity for how the process should be terminated.
Fix #51021
Contributes to #31541