Zeva
New Member
- Messages
- 1
- Reaction score
- 0
Game Version
v2026.9.10.5438
Operating System
Bazzite Linux
CPU: AMD Ryzen 7 9800X3D
GPU: AMD Radeon RX 9070 XT
RAM: 32 GB
Mods: Core only, no mods enabled.
What Happened
While flying a vehicle in Map View, I had the floating BURN panel open. I dragged the BURN panel toward the right side of the screen. Immediately after repositioning it, the game UI froze. KSA subsequently logged an unhandled exception and terminated with SIGABRT.
The relevant exception was:
I had a rolling screen recording active during the incident.
In the attached sanitized video, the final continuous frozen frame begins at approximately 00:29.92, when only the mouse moves but the game. Immediately before this, the BURN panel can be seen being dragged/repositioned.
The timing of the visible freeze correlates with the logged exception to within approximately 0.87 seconds.
Important: the video does not prove that I clicked one of the "+" controls. The mouse pointer is near the upper-right controls immediately before the freeze, but there is no visible button press transition.
There is also no visible NaN, Infinity, error string, or obviously invalid numerical value displayed in the BURN panel before the crash.
What Was Expected
Dragging/repositioning the floating BURN panel should not freeze or terminate the game.
If an invalid internal time value is generated while processing the BURN UI, it should not result in an unhandled exception terminating KSA.
Reproduction Steps
I have not intentionally reproduced this yet, so these are the exact circumstances of the captured incident rather than confirmed 100% reproduction steps:
The exception stack indicates that KSA was executing
However, I cannot confirm from the video that I intentionally clicked a "+" button while moving the panel.
Reproduction Rate
Observed once.
I have not yet attempted to reproduce it intentionally.
Additional Info
The incident was captured with application, process and system monitoring running.
No evidence of the following was found around the crash:
KSA was using approximately 5.5 GiB RSS immediately before the crash. The system still had substantial available memory and no swap pressure.
The attached short video is a sanitized 37-second extract of the original replay. The visible freeze begins at approximately 00:29.92.
Attachments
A full systemd coredump has also been preserved and can be provided privately to a RocketWerkz developer on request.
I have also preserved:
The full coredump is approximately 2.6 GiB compressed and has not been uploaded publicly because it can contain sensitive process memory. I can provide it privately if a RocketWerkz developer needs it.
The relevant save/vehicle files are also available if they would help investigation.
v2026.9.10.5438
Operating System
Bazzite Linux
CPU: AMD Ryzen 7 9800X3D
GPU: AMD Radeon RX 9070 XT
RAM: 32 GB
Mods: Core only, no mods enabled.
What Happened
While flying a vehicle in Map View, I had the floating BURN panel open. I dragged the BURN panel toward the right side of the screen. Immediately after repositioning it, the game UI froze. KSA subsequently logged an unhandled exception and terminated with SIGABRT.
The relevant exception was:
Code
System.ArgumentException: Cannot construct a UniverseTime from NaN
at KSA.UniverseTime.NanosecondsFromSeconds(Double seconds)
at KSA.UniverseTime.op_Addition(UniverseTime a, Double b)
at KSA.Burn.PlusClicked(FlightComputer flightComputer)
at KSA.GaugeButtonBurn.OnActivated(Double multiplier)
at KSA.GaugeButtonBinding.OnClicked(SoundReference sound)
at KSA.GaugeButtonReference.OnClicked()
at KSA.GaugeComponent.OnClicked(float2 canvasUv)
at KSA.GaugeCanvas.OnClicked(float2 canvasUv)
at KSA.Program.OnDrawUiThreadSafe(Double dt)
at KSA.Program.OnFrame(Double currentPlayerTime, Double dtPlayer)I had a rolling screen recording active during the incident.
In the attached sanitized video, the final continuous frozen frame begins at approximately 00:29.92, when only the mouse moves but the game. Immediately before this, the BURN panel can be seen being dragged/repositioned.
The timing of the visible freeze correlates with the logged exception to within approximately 0.87 seconds.
Important: the video does not prove that I clicked one of the "+" controls. The mouse pointer is near the upper-right controls immediately before the freeze, but there is no visible button press transition.
There is also no visible NaN, Infinity, error string, or obviously invalid numerical value displayed in the BURN panel before the crash.
What Was Expected
Dragging/repositioning the floating BURN panel should not freeze or terminate the game.
If an invalid internal time value is generated while processing the BURN UI, it should not result in an unhandled exception terminating KSA.
Reproduction Steps
I have not intentionally reproduced this yet, so these are the exact circumstances of the captured incident rather than confirmed 100% reproduction steps:
- Fly a vehicle and enter Map View.
- Have a burn/maneuver displayed in the floating BURN panel.
- Drag/reposition the BURN panel.
- In this incident, KSA froze immediately after the panel was repositioned.
The exception stack indicates that KSA was executing
KSA.Burn.PlusClicked when the invalid UniverseTime was constructed.However, I cannot confirm from the video that I intentionally clicked a "+" button while moving the panel.
Reproduction Rate
Observed once.
I have not yet attempted to reproduce it intentionally.
Additional Info
The incident was captured with application, process and system monitoring running.
No evidence of the following was found around the crash:
- AMDGPU/DRM reset or GPU hang
- Vulkan/Mesa failure
- OOM killer or memory-cgroup kill
- Kernel panic
KSA was using approximately 5.5 GiB RSS immediately before the crash. The system still had substantial available memory and no swap pressure.
The attached short video is a sanitized 37-second extract of the original replay. The visible freeze begins at approximately 00:29.92.
Attachments
README.txt- concise incident summary including KSA version, system specs, crash description, relevant stack trace, replay timing/correlation, and notes about additional preserved evidence available on request.ksa-context-before-crash.txt- KSA log context immediately preceding the crashksa-unhandled-exception.txt- isolated unhandled exception and stack tracelastchance-context.txt- relevant LastChance contextlastchance-exception.txt- isolated LastChance exceptionreplay-trimmed-for-ahwoo.zip- sanitized 37-second MP4 replay; visible freeze begins at approximately 00:29.92
A full systemd coredump has also been preserved and can be provided privately to a RocketWerkz developer on request.
I have also preserved:
- KSA final/ring logs
- LastChance/crash log
- systemd coredump metadata
- the full Linux systemd coredump
The full coredump is approximately 2.6 GiB compressed and has not been uploaded publicly because it can contain sensitive process memory. I can provide it privately if a RocketWerkz developer needs it.
The relevant save/vehicle files are also available if they would help investigation.
Upvote
0
