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
Rendering can stop working in a long running application #2084
Comments
Hmm does the app need to be focused or not? |
It does not seem to matter if it is foreground or not |
I can't reproduce it. I have run the fyne_demo for almost 6 hours, and it still works great. |
Hmm, that is good to hear, in a way. Perhaps this is specific to:
|
Yes, it could be, although now I realized that I tested it on |
I have seen this happen since late development of v2.0.0, so I think it is present in all the branches you listed |
I thought it was a bug in FyneDesk but then it occurred on another app. |
Hmm, do they have something in common? |
The only thing that seems to apply to both is the computer they were running on honestly. I have done a complete OS update and restart and will see if the same occurs, this may have been a red herring and/or less common issue than I thought. |
A whole day running and it's not happened again. Closing unless anyone else experiences this |
Unclear what is going on here.
It is possible that the UI stops responding.
The app continues to work (i.e. buttons tap, console logs etc) just the UI stops changing.
May relate to #950.
May be caused by some GPU constraints - does not seem to be a traditional memory leak as plenty free RAM.
To Reproduce:
Steps to reproduce the behaviour:
Device (please complete the following information):
The text was updated successfully, but these errors were encountered: