Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
has your system been running for some while? i have observed this behaviour in niri (a separate wm) as well, and seemingly, it is not a issue. if i understand it correctly, for any app that had vrma allocated, and is closed it's vram is not cleared correctly (on amd i gpu) and that usage just gets added to wm (the host program). if it is not using much gpu (check any app which shows usage), then it is just a reporting issue. like when i fresh boot, my wm uses 100MiB of vram, but with time, it becomes 2GiB and stays there, but i still can open stuff which requires vram. kinda like buffered ram, which is still allocated, but available to use.
I've seen it hit higher numbers within a day of booting. It's fairly recent behavior, so I think an update broke something and was hoping another update would fix it. That hasn't happened yet, so I may need to do some troubleshooting.