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

Check memory usage of staticcheck on github.com/fyne-io/fyne #825

Closed
dominikh opened this issue Sep 14, 2020 · 4 comments
Closed

Check memory usage of staticcheck on github.com/fyne-io/fyne #825

dominikh opened this issue Sep 14, 2020 · 4 comments
Assignees

Comments

@dominikh
Copy link
Owner

People have reported OOMs in Travis.

@Jacalz
Copy link

Jacalz commented Feb 1, 2021

I think you can close this. Our issues has gone away after some changes in Fyne in combination the latest staticcheck releases. Thanks for making the best static analysis available 🙂

@dominikh
Copy link
Owner Author

dominikh commented Feb 1, 2021

That's good to hear, but now I'm even more curious to find out what specific change in Fyne fixed it. September 2020 to January 2021 should be a small enough range to be able to bisect this nicely.

I'll definitely still look into this at some point.

@Jacalz
Copy link

Jacalz commented Feb 1, 2021

Ah, I see. Sorry, I should have attached a link to the changes. It was largely fixed by fyne-io/fyne#1638 which changed the bundled (or embedded if you may) resources from being []byte to string. This was initially brought up in fyne-io/fyne#1436 due to the severe memory usage issues that I had reported to gopls. It is also becoming much less of an issue now that we have go:embed in Go 1.16, though I guess there might still be some cases where large slices could cause excessive memory usage.

@dominikh
Copy link
Owner Author

dominikh commented Feb 1, 2021

Ah, I see. I am going to close this, then. A large portion of the memory usage seems to be in go/ast and go/types. Our IR is piling on even more memory usage, but that's indirectly tracked by #618. And you're right about go:embed making this issue less important.

Thanks for the update.

@dominikh dominikh closed this as completed Feb 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants