Add delay in search_universe to prevent SteamVR lockup #27
Conversation
Recently, I've been experiencing VR lockups where SteamVR suddenly stops sending video via SteamLink, and then eventually crashes. Around the time that SteamVR locks up, I see the following rapid log spam in `vrserver.txt`: ``` Sun May 04 2025 16:58:32.523 [Info] - slimevr: Error getting universes from "C:\Program Files (x86)\Steam\config\chaperone_info.vrchap": IO_ERROR: Error reading the file. Sun May 04 2025 16:58:32.523 [Info] - slimevr: Failed to find current universe! Sun May 04 2025 16:58:32.524 [Info] - slimevr: Error getting universes from "C:\Program Files (x86)\Steam\config\chaperone_info.vrchap": IO_ERROR: Error reading the file. Sun May 04 2025 16:58:32.524 [Info] - slimevr: Failed to find current universe! Sun May 04 2025 16:58:32.529 [Info] - slimevr: Error getting universes from "C:\Program Files (x86)\Steam\config\chaperone_info.vrchap": IO_ERROR: Error reading the file. Sun May 04 2025 16:58:32.529 [Info] - slimevr: Failed to find current universe! Sun May 04 2025 16:58:32.533 [Info] - slimevr: Error getting universes from "C:\Program Files (x86)\Steam\config\chaperone_info.vrchap": IO_ERROR: Error reading the file. Sun May 04 2025 16:58:32.534 [Info] - slimevr: Failed to find current universe! Sun May 04 2025 16:58:32.539 [Info] - slimevr: Error getting universes from "C:\Program Files (x86)\Steam\config\chaperone_info.vrchap": IO_ERROR: Error reading the file. Sun May 04 2025 16:58:32.539 [Info] - slimevr: Failed to find current universe! ``` During normal operation, there is no such log spam. I can't prove if the SteamVR lockup causes this log spam, or whether this error causes SteamVR to eventually lockup. However, when I introduce a delay in `search_universe` to prevent a rapid loop of requests to SteamVR, I don't encounter the crash anymore.
|
@kitlith any ideas on how to confirm or deny this hypothesis? |
|
Well, there's some interesting shit happening here. That log spam is from the driver: https://github.com/SlimeVR/SlimeVR-OpenVR-Driver/blob/760eb1a3f8ba503fde48f29e0bface9566a97eab/src/VRDriver.cpp#L122 I'd like to get more imformation on that IO_ERROR, if it only occurs suddenly. Wait. There's no log spam in normal circumstances? I was under the impression that the driver would fail to find the universe, and thus always spam, with steamlink. |
|
I remember at some point (even before SteamLink was a thing) I was running into driver spamming logs there, it's fixed in my PR SlimeVR/SlimeVR-OpenVR-Driver#38 @ https://github.com/SlimeVR/SlimeVR-OpenVR-Driver/blob/538b1fe57958d7a7277cded89f1fc4cc7c33adf1/src/VRDriver.cpp#L84. |
|
@jabberrock does the lock-up still occur with the latest version of the driver? |
3 participants
Recently, I've been experiencing VR lockups where SteamVR suddenly stops sending video via SteamLink, and then eventually crashes. Around the time that SteamVR locks up, I see the following rapid log spam in
vrserver.txt:During normal operation, there is no such log spam.
I can't prove if the SteamVR lockup causes this log spam, or whether this error causes SteamVR to eventually lockup. However, when I introduce a delay in
search_universeto prevent a rapid loop of requests to SteamVR, I don't encounter the crash anymore.