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

[BUG] VRAM text value is stuck at 0.5GB #63

Open
siferati opened this issue Mar 9, 2025 · 0 comments
Open

[BUG] VRAM text value is stuck at 0.5GB #63

siferati opened this issue Mar 9, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@siferati
Copy link

siferati commented Mar 9, 2025

Describe the bug
The text value of the GPU VRAM consumption is stuck at 0. 5GB.
The visual representation (ring graph or bar graph) is correct -- the percentage usage matches the value from HWiNFO.
But the text value is always showing 0.5 GB, independently of the actual usage.

Expected behavior
Text value of VRAM shows the correct amount.

Screenshots

Notice how the text is showing 0.5 GB even though the ring graph is correctly showing ~50% usage (which should be ~ 2 GB)
The ring graph correctly updates in real time and matches the value shown by HWiNFO.
But the text value is always stuck at 0.5 GB regardless.

Image Image

Also not sure if it's related, but even though I'm selecting the GPU Memory sensor, when I click on the drop down again it shows the checkmark in the wrong sensor.
This checkmark bug doesn't happen in the other sensors, only in this one -- so maybe it's related.

Image Image

Desktop (please complete the following information):

  • OS: Windows 11 24H2
  • Version 1.1.0
@siferati siferati added the bug Something isn't working label Mar 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant