Skip to content
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

Closed
andydotxyz opened this issue Mar 12, 2021 · 10 comments
Closed

Rendering can stop working in a long running application #2084

andydotxyz opened this issue Mar 12, 2021 · 10 comments
Labels
blocker Items that would block a forthcoming release bug Something isn't working not an issue This doesn't seem right

Comments

@andydotxyz
Copy link
Member

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:

  1. Run any app for a long time
  2. See that UI can stop responding

Device (please complete the following information):

  • OS: Arch Linux
  • Version: latest
  • Go version: 1.15
  • Fyne version: 2.0.1
@andydotxyz andydotxyz added bug Something isn't working blocker Items that would block a forthcoming release labels Mar 12, 2021
@fpabl0
Copy link
Member

fpabl0 commented Mar 13, 2021

Run any app for a long time

Hmm does the app need to be focused or not?

@andydotxyz
Copy link
Member Author

It does not seem to matter if it is foreground or not

@fpabl0
Copy link
Member

fpabl0 commented Mar 14, 2021

I can't reproduce it. I have run the fyne_demo for almost 6 hours, and it still works great.

@andydotxyz
Copy link
Member Author

Hmm, that is good to hear, in a way.

Perhaps this is specific to:

  • Running on (arch) linux?
  • Having FyneDesk running
  • A problem with my Arch linux install or ageing XPS laptop

@fpabl0
Copy link
Member

fpabl0 commented Mar 14, 2021

Yes, it could be, although now I realized that I tested it on develop branch, could it be that this is fixed on develop but not in 2.0.1?

@andydotxyz
Copy link
Member Author

I have seen this happen since late development of v2.0.0, so I think it is present in all the branches you listed

@andydotxyz
Copy link
Member Author

I thought it was a bug in FyneDesk but then it occurred on another app.

@fpabl0
Copy link
Member

fpabl0 commented Mar 17, 2021

Hmm, do they have something in common?

@andydotxyz
Copy link
Member Author

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.

@andydotxyz
Copy link
Member Author

A whole day running and it's not happened again. Closing unless anyone else experiences this

@andydotxyz andydotxyz added the not an issue This doesn't seem right label Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker Items that would block a forthcoming release bug Something isn't working not an issue This doesn't seem right
Projects
None yet
Development

No branches or pull requests

2 participants