- Joined
- Mar 31, 2023
- Messages
- 445
- Solutions
- 15
- Reactions
Has anyone else experienced VaM crashing only in VR recently this week? It crashes immediately after loading any scene or shortly after loading a scene. I suspect that the beta update for SteamVR released a few days ago may be the cause. Rolling back to the main branch or using Open Composite instead seems to stop the crashing.
Sometimes SteamVR and the headset driver itself will crash as well. I've checked Event Viewer and it usually shows a Warning from "Resource-Exhaustion-Detector" about "Windows successfully diagnosed a low virtual memory condition." imminently before all the crashing events. I know VaM can sometimes cause this on its own, but I have 32GB system ram and rarely encountered that problem before.
Anyways, since I saw that Warning I started out trying to fix it by removing several var packages like ones reported by the morphbloatscanner python script. Then I tried adjusting my system paging file to see if that changed anything. Finally, I came around to the idea of trying Open Composite and that's when I first found something that actually made a difference. From there I decided to see if changing versions of SteamVR would work and it did.
One conclusion I can come to is that maybe this recent SteamVR beta is causing some kind of memory leak. Also, I noticed the first time after it updated that Windows gave me one of those confirmation prompts about allowing changes to be made which was weird.
My system specs if it matters:
OS: Windows 10 22H2
Memory: 32GB RAM (Corsair DDR4-3200 using XMP profile)
CPU: Intel i7-11700KF
GPU: Radeon 6800 XT
Headset: HP Reverb G2
Storage: SanDisk Extreme Pro Portable SSD (exclusively for VaM)
Sometimes SteamVR and the headset driver itself will crash as well. I've checked Event Viewer and it usually shows a Warning from "Resource-Exhaustion-Detector" about "Windows successfully diagnosed a low virtual memory condition." imminently before all the crashing events. I know VaM can sometimes cause this on its own, but I have 32GB system ram and rarely encountered that problem before.
Anyways, since I saw that Warning I started out trying to fix it by removing several var packages like ones reported by the morphbloatscanner python script. Then I tried adjusting my system paging file to see if that changed anything. Finally, I came around to the idea of trying Open Composite and that's when I first found something that actually made a difference. From there I decided to see if changing versions of SteamVR would work and it did.
One conclusion I can come to is that maybe this recent SteamVR beta is causing some kind of memory leak. Also, I noticed the first time after it updated that Windows gave me one of those confirmation prompts about allowing changes to be made which was weird.
My system specs if it matters:
OS: Windows 10 22H2
Memory: 32GB RAM (Corsair DDR4-3200 using XMP profile)
CPU: Intel i7-11700KF
GPU: Radeon 6800 XT
Headset: HP Reverb G2
Storage: SanDisk Extreme Pro Portable SSD (exclusively for VaM)
