[GH-ISSUE #293] (Nvidia) VRAM leak when restarting stream #203

New issue

Closed

opened 2026-10-15 12:58:09 +00:00 by bsakaguchi · 2 comments

bsakaguchi commented

2026-10-15 12:58:09 +00:00

Owner

Originally created by @zexi on GitHub (Nov 19, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/293

After repeatedly starting the Steam container and then exiting it by invoking "Quit Game" in the Moonlight client, I noticed the VRAM usage by the Wolf process keeps increasing with each cycle.

Originally created by @zexi on GitHub (Nov 19, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/293 After repeatedly starting the Steam container and then exiting it by invoking "Quit Game" in the Moonlight client, I noticed the VRAM usage by the Wolf process keeps increasing with each cycle. <img width="993" height="551" alt="Image" src="https://github.com/user-attachments/assets/41c25332-b4e7-4d95-b0f0-2f425fbf8834" /> <img width="850" height="148" alt="Image" src="https://github.com/user-attachments/assets/66a0a542-c8bc-4726-bb4b-e8fd8d60152f" />

bsakaguchi

2026-10-15 12:58:09 +00:00

closed this issue
added the
nvidia

bug
labels

bsakaguchi commented

2026-10-15 12:58:10 +00:00

Author

Owner

@ABeltramo commented on GitHub (Nov 22, 2025):

Thanks for opening this, I completely missed it!
I guess I was just too focused on the GPU usage and avoid leaking memory whilst streaming that I haven't checked if we were leaking memory between streams. I've just merged a fix, latest wolf:stable should correctly clean up the memory after a stream closes.

It'll still keep ~150MB of memory around after the first stream is started, but that's a one time thing that I'll address in a separate PR. I just wanted to fix this quickly because a leak has the maximum priority. Let me know if this fixes it for you too.

@ABeltramo commented on GitHub (Nov 22, 2025): Thanks for opening this, I completely missed it! I guess I was just too focused on the GPU usage and avoid leaking memory whilst streaming that I haven't checked if we were leaking memory between streams. I've just merged a fix, latest `wolf:stable` should correctly clean up the memory after a stream closes. It'll still keep ~150MB of memory around after the first stream is started, but that's a one time thing that I'll address in a separate PR. I just wanted to fix this quickly because a leak has the maximum priority. Let me know if this fixes it for you too.

bsakaguchi commented

2026-10-15 12:58:11 +00:00

Author

Owner

@zexi commented on GitHub (Nov 23, 2025):

Thanks for the quick fix. The latest wolf:stable image fixes this and no VRAM leak anymore.

@zexi commented on GitHub (Nov 23, 2025): Thanks for the quick fix. The latest `wolf:stable` image fixes this and no VRAM leak anymore.