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

High GPU memory usage #39

Open
HON95 opened this issue Nov 24, 2022 · 3 comments
Open

High GPU memory usage #39

HON95 opened this issue Nov 24, 2022 · 3 comments

Comments

@HON95
Copy link

HON95 commented Nov 24, 2022

According to nvidia-smi, iwgtk is currently using 460MB of my GPU memory. That's a lot, and I don't see why this should be using GPU memory at all.

It seems like every time I open the window from tray and then close it again it consumes another ~30MB, and it just keeps climbing when I open and close it repeatedly (e.g. by spam-clicking the tray icon). Clearly a memory leak somewhere.

Then again, why is this using GPU memory in the first place? Is that some kind of requirement for GTK apps or something?

Using:

  • Arch Linux (latest as of yesterday)
  • i3 4.21.1
  • Xorg (xorg-server) 21.1.4-1
  • iwgtk 0.8
@HON95
Copy link
Author

HON95 commented Nov 24, 2022

Opening it enough times to eat all of my 10GiB of GPU memory makes the window visually corrupted, so clearly the GUI is using some kind of video acceleration.

@J-Lentz
Copy link
Owner

J-Lentz commented Nov 28, 2022

GTK4 does use a lot of GPU memory, some of which is due to caching and some of which may be an artifact of how GPU memory usage is reported. See: https://www.reddit.com/r/GTK/comments/vv55p4/gtk4_memory_usage_unexpectedly_high/

However, the ~30 Mb memory leak is most likely due to iwgtk failing to free something, rather than a bug in the toolkit.

@w-jablonski
Copy link

Has this memory leak been fixed or looked into? Thanks for your time

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants