-
-
Notifications
You must be signed in to change notification settings - Fork 202
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] When "Show PC Uptime" is enabled, steady high CPU usage #743
Comments
Give the latest nightly build a try, I couldn't replicate this issue but if it was the cause it should be fixed now. |
Hi, thank you for trying to fix my issue. The only log i got with this version is this: 2024-03-16 15:34:11.6148 [INFO ] VRCX - VRCX Nightly 2024-03-15T15.08-0b64416 and it closes/crashes itself shortly after starting VRCX. is there anything further i could do to help you? |
Does the nightly version before this one work? can you check if your anti virus is affecting anything? |
Actually yeah, that was the version i was running prior. I got it working now. It crashed right there: I dont have the exact error message anymore and i cant recreate it but it said like my System.Diagnostics.PerformanceCounter.dll could be corrupted or something like that. Im sorry for your troubles. |
Thanks for looking deep into it makes my life much easier, interesting.... I guess I'll add |
Describe the bug
If i turn on the option "Show PC Uptime" in "Wrist Overlay" i get a constant CPU Usage of about 5%.
This even if no SteamVR or VRChat is running.
Disabling this Option fixes it and the CPU usage is down again.
To Reproduce
If i turn this option on or off i get instant high/low CPU usage.
When i give my sqlite db to a friend, his CPU did not Spike, even when activating this option.
So i guess this has to do something with my PC.
Expected behavior
Dont spike my CPU usage like that.
Screenshots
What version you are running
Currently running 2024-03-04T23.20 (but had issues before that a long time)
AMD R7 5800X
Windows 10 (German)
Is there additional Information i can provide to assist you in finding this bug?
The text was updated successfully, but these errors were encountered: