OyasumiVR
OyasumiVR copied to clipboard
Subprocess "overlay-sidecar.exe" might have memory leak
Sometimes process called "overlay-sidecar.exe" eat up entire RAM on a machine.
I activated "Memory Watcher" feature, then popup window alert constantly spams.
Thanks for reporting. That's very odd. Although there have been memory issues in the past, none of them have happened in the overlay module yet. The next time this happens, would you mind sharing your log file with me? You'll be able to find it at %APPDATA%\co.raphii.oyasumi\logs\OyasumiSidecar.log
.
In the meantime, I'll see if I can add some useful memory profiling to the overlay module in an upcoming release.
I'll attach OyasumiSidecar_20240308.log
, which should be a log file contains the event, instead, since the specified file seems not be written recently.
OyasumiVR_Overlay_Sidecar_20240308.log
In my environment, overlay-sidecar,exe
consumes over 1.7 GB of memory as soon as I launch Oyasumi VR application, and I can see the RAM usage goes up slowly. Changing brightness on the app, RAM usage seems to go up by a some hundreds KB.
Gotcha. The logs sadly don't say much. The ram usage increasing a bit when you change brightness is expected, but that initial 1.7GB really shouldn't be happening. Here the overlay uses about 80MB after starting, with SteamVR running.
- Is there a difference in memory use between launching OyasumiVR with SteamVR already running, and without SteamVR already running? (And does this changes when you launch SteamVR after?)
- Could you try and see if this happens on the new beta version? You can get it by switching to the beta branch on Steam, and then optionally verifying integrity on your install files. You'll know you're on the right build if you find the build number
d3e2a0c
in the about view.
- There is no difference between with or without Steam VR already running.
- Beta build
d3e2a0c
seems not solved this problem; it still consume 1.7GB of RAM...
Additionally, I found that opening overlay menu in VR cause massive memory usage increase (about 500MB/s).
I seem to have absolutely no way of reproducing this, so I sadly cannot do much about it currently.
I'll leave this issue open in case more people are experiencing this, or maybe get some insights from someone who knows why it might be happening.
If someone happens to run into this, please send me a memory dump on Discord (before killing the overlay)
You can just right click the overlay-sidecar.exe process in task manager, and click "Create memory dump file"