mirror of
https://github.com/games-on-whales/wolf-ui.git
synced 2026-10-15 13:02:04 +00:00
[GH-ISSUE #11] wolf-ui crashes with "invalid opcode" (ud2 / Rust panic) #9
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf-ui#9
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 @n0pashkov on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/games-on-whales/wolf-ui/issues/11
Environment:
Symptom:
wolf-ui crashes every session with:
traps: wolf-ui[PID] trap invalid opcode ip:4799c0 sp:... error:0
Analysis:
Disassembly at 0x4799c0 shows ud2 instruction after a function call —
Rust panic. Crash happens after:
call 0x312ef90 ;
0f 0b ; ud2 ← crash here
After crash, wolf container restarts and Moonlight session is disconnected.
System becomes unstable with kernel page faults following the crash.
Steps to reproduce:
@Skerga commented on GitHub (Mar 28, 2026):
Could you attach the full wolf log with
WOLF_LOG_LEVEL=DEBUGset. This should hopefully give some information if something breaks in wolf already that's then passed to wolf-ui and it should also capture the logs of wolf-ui itself. And to be safe could you also add the wolf-ui's container log.What's making me wonder is that it's something rust related from what you've wrote, but wolf-ui isn't written in rust so the only thing rust related could come from the base image. But all wolf application images are based on that and this is the first time I've heard about such a crash.