mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #231] Wolf crash when trying to exit on switch moonlight client #159
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#159
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KevinBonnoron on GitHub (Jul 20, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/231
Hello.
I am not sure if I should report this issue to this repo or to the moonlight switch app, but whenever I try to exit an app from the switch moonligh client (by pressing plus and minus at the same time), the wolf container crash. Any other moonlight clients are also disconnected are not able to reconnect until I restart wolf container. I noticed that the app containers are still running but from moonlight client the server is considered as offline.
Here is the log in the wolf container when I try to quit the app:
Here is the log inside the steam container that I tryed to quit:
This doesn't happend for linux or windows moonlight clients. So I am not sure this is related to wolf.
Could you help me please?
Regards
@ABeltramo commented on GitHub (Jul 20, 2025):
That's a Wolf C++ exception out in the wild (
map::at)!I'm afraid you've cut the logs too early.. Could you please add the env variable
WOLF_LOG_LEVEL=DEBUGand post the full logs up until the exception and possibly the stacktrace after you restart Wolf?@KevinBonnoron commented on GitHub (Jul 20, 2025):
Here is the full log
I upload the .dump too (had to rename it to .txt because github don't accept .dump files).
Thanks for your help!
backtrace.dump.txt
@ABeltramo commented on GitHub (Jul 20, 2025):
I thought it was something with the virtual Nintendo joypad, but I can't replicate it on my end when using a normal Moonlight client. I was tempted to revive my Nintendo Switch, but the back is worryingly expanding (I haven't used it for the past year or so), I'll order a cheap replacement battery..
In the meantime, the log above seems to trigger the exception on stream start, which doesn't track with what you originally said. Can you explain in more detail the issue? Maybe with a video recording?
@KevinBonnoron commented on GitHub (Jul 21, 2025):
In the last log I've triggered the plus+minus key combination a few seconds after steam container starts. Maybe the container was not fully started when I tryed the combination?
The error appear exactly when I press the key combination. It display a little moonlight menu on top of the current application allowing me to either quit / close the application. As soon as this menu appear, the error get triggered in the console. Maybe the stream should be in "pause" mode while this menu is visible?
Here is another log I get if I don't do any action after pressing plus+minus:
Then nothing more in the console. The app crash on moonlight client after a few seconds (with no error). I am not disconnected from the server but I can't launch any application. If I disconnect I can't reconnect until I restart wolf.
Thanks!
@KiringD commented on GitHub (Jul 21, 2025):
I can confirm that this issue occurs when interacting with the Moonlight application's overlay on Switch. The error occurs when opening the overlay, or, for example, when trying to change the on-screen keyboard language.
@ABeltramo commented on GitHub (Jul 23, 2025):
Got the battery replacement and I could easily replicate the issue, oddly the Moonlight Switch client was sending a weird keyboard character when pressing
-and+which was triggering a dumb exception on our side.:stableis building right now, once a new image is available you can just update Wolf usingand re-launch the container. Feel free to re-open if this doesn't fix it for you too!
@Trasen commented on GitHub (Jul 23, 2025):
Is it handled for all unknown characters now or just those specific ones?
@ABeltramo commented on GitHub (Jul 23, 2025):
That exception should never occur again, if there's an unknown character we just drop it now and log a warning in the logs. 😉
@KevinBonnoron commented on GitHub (Jul 24, 2025):
Tested quickly this morning. Working great. Thanks!