This repository was archived by the owner on Oct 13, 2021. It is now read-only.
CPU resources are not released after the app exits.#152
Open
akatsuki105 wants to merge 1 commit intomarcusolsson:masterfrom
Open
CPU resources are not released after the app exits.#152akatsuki105 wants to merge 1 commit intomarcusolsson:masterfrom
akatsuki105 wants to merge 1 commit intomarcusolsson:masterfrom
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Hello. I use your framework to develop a TUI file dialog, "tfd".
This framework is great! But seems to have one bug.
Apps created using this framework will not release CPU resources even if exit with ui.Quit().
For example, if you put time.Sleep(time.Second*10) in the last line in tui-go/example/login/main.go, you can confirm that the CPU resources are not released.
I don't know the details of this framework, but I thought this bug is caused by the for-loop in ui.Run() being kept running.