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

Closing "kitty" terminal causes VRAM usage to permanently increase #1562

Open
GallowsDove opened this issue Oct 15, 2024 · 6 comments
Open

Comments

@GallowsDove
Copy link

When you open a new "kitty" window, nothing special happens (as you would expect), however when you close the window VRAM usage increases by varying amount, depending on the size of the window.

I've noticed this issue when looking at another issue with increasing VRAM caused by NVIDIA.

The issue could be unrelated, since someone mentioned something similar happening on AMD, however since I don't have an AMD card, I can't test it.

Tested with (positively):

  • Niri
  • Cosmic

Tested and not impacted:

  • River
  • Hyprland
  • Sway
@GallowsDove
Copy link
Author

possibly related issue: hyprwm/Hyprland#357

@GallowsDove GallowsDove reopened this Oct 15, 2024
@GallowsDove GallowsDove changed the title Opening and closing "kitty" terminal causes VRAM usage to permanently increase Closing "kitty" terminal causes VRAM usage to permanently increase Oct 15, 2024
@TheCodedProf
Copy link

Can confirm the same issue with an AMD card on Niri (have not tested elsewhere atm, but will try to do so when I'm home).

@GallowsDove
Copy link
Author

Edit: Does not seem to happen in anvil, but still find it weird that it happens both in cosmic and niri. Should I just report it to the respective compositors?

@vfosterm
Copy link

I think this is a general issue with the NVIDIA drivers when explicit sync is enabled. I'm using Hyprland and it definitely repros there when enabling explicit sync.

Limiting the free buffer pool for the compositor on the nvidia side is a functioning workaround for me. Haven't noticed any side effects and I'm able to use explicit sync again.

Details here:
NVIDIA/egl-wayland#126 (comment)

@GallowsDove
Copy link
Author

GallowsDove commented Oct 31, 2024

I think this is a general issue with the NVIDIA drivers when explicit sync is enabled. I'm using Hyprland and it definitely repros there when enabling explicit sync.

Limiting the free buffer pool for the compositor on the nvidia side is a functioning workaround for me. Haven't noticed any side effects and I'm able to use explicit sync again.

Details here:
NVIDIA/egl-wayland#126 (comment)

Like I said, that is probably a completly unrelated issue. Yes, NVIDIA as such has issues, however the VRAM leak happens for me even with the workaround active. And it was also reproduced on AMD gpu.

And like I said, I didn't notice the issue on hyprland.

when explicit sync is enabled

is there a way to reproduce it on hyprland? does something specific have to be set? because hyprland didn't have the leak when I tested it (with the workaround active), and both Niri and Cosmic do.

@xcccdjsn
Copy link

xcccdjsn commented Nov 3, 2024

Also wezterm can cause memory leaking. Maybe other application I has not tested occurs same result.. I used wezterm, kitty and many screen lockers in dwl that does not cause memory leaking. In dwl, it will release the related memory usage qucikly after closing application in using.

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

4 participants