Xrizer crash/panic due to failed protected memory read/write #6022
Description
Describe the bug?
Splicing the bits of this error together. Sources noted.
Visual: Resonite will hang for a moment, then close down.
Steam terminal (running to catch this error stack)
Fatal error.
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
^CSteam Runtime Launch Service: steam-runtime-launcher-service pid 197369 exited
Steam Runtime Launch Service: starting steam-runtime-launcher-service
Steam Runtime Launch Service: steam-runtime-launcher-service is running pid 204714
bus_name=com.steampowered.PressureVessel.LaunchAlongsideSteam
Aborted (core dumped)
Game Recording - game stopped [gameid=2519830]
["removing process" list omitted]
2025-12-17T19:01:14.354 ERROR xrizer ThreadId(2)] panicked at library/core/src/panicking.rs:225:5:
panic in a function that cannot unwind
[2025-12-17T19:01:14.354 ERROR xrizer ThreadId(2)] Backtrace:
0: xrizer::init_logging::{{closure}}::{{closure}}
1: std::panicking::panic_with_hook
2: std::panicking::panic_handler::{{closure}}
3: std::sys::backtrace::__rust_end_short_backtrace
4: __rustc::rust_begin_unwind
5: core::panicking::panic_nounwind_fmt
6: core::panicking::panic_nounwind
7: core::panicking::panic_cannot_unwind
8: openvr::bindings::vr::ivrcompositor022::WaitGetPoses
9: IVRCompositor_IVRCompositor_022_WaitGetPoses
10: __wine_unix_call_dispatcher
11: start_thread
12:
13:
The Resonite log itself tends to just stop being written. I have not seen any correlation between the Resonite logs during this bug. I will attach the last one anyway.
To Reproduce
Launch Resonite, interact and go about your day until it occurs.
Reproduction Item/World
N/A
Expected behavior
No crash please?
Screenshots
No response
Resonite Version Number
Beta 2025.12.16.1424
What Platforms does this occur on?
Linux
What headset if any do you use?
CV1
Log Files
KamiGeneration1 - 2025.12.16.1424 - 2025-12-17 18_11_11.log
Additional Context
Possibly .Net related?
According to Micro$oft, this may be resolved by using ANSI-92 format.
Reporters
Inucune