feat: crash reports sent from the game to a bot (with consent) #81
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#81
Loading…
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?
Why
When Longshot crashes, the player has to find the log, open an issue or a Discord message, and paste it by hand. Most
don't, so we only hear about a fraction of crashes, often without the version, the GPU or the backtrace. A bot that
receives a crash report straight from the game would tell us how often each crash happens and on which hardware.
What we already have
On a crash, the handler in
host/mkw_glue.c(report_crash) writes to the log:CRASH: exception <code> (<read|write> <addr>, guest <addr>) at <module>+<offset>CRASH: host backtrace: <module>+<offset> ...(x64 unwind data on Windows,backtrace()on Linux)and
log_crash_filter(host/hos_thread.c) drains the log queue before the process dies. So the summary of a crashis already there; it never leaves the PC.
Proposal
"Longshot closed unexpectedly last time. Send a crash report?" with Send, Don't send and Always send.
Nothing is sent without that consent, and it can be turned off in the settings.
CRASH:lines and the last ~200 lines of the log before thempaths: user names in paths become
<user>.MagicBeanDev/Infra), which:#crash-reportschannel, and counts the rest on the samemessage (versions, GPUs and OSes seen)
crash) once a signature reaches a few reports, linking the Discord message, andcomments on it when a new version still crashes the same way
turn the top frames into function names for the post.
Open questions
only?
Done when
#crash-reportswith its version, hardware andbacktrace, and nothing is sent without consent.
tests/has a check that the report builder leaves out paths and game data (no game needed).Crash: 0xc0000005 (read) at
livetest.exe+0xdeadin0.0.0-livetest8184a6f2e233· seen 4 times · first 2026-11-13 02:39 UTC · last 2026-11-13 03:10 UTC0.0.0-livetest(4)Live test from Bean-Ops (Linux)(3),Live test from Bean-Ops (Windows 11)(1)Vulkan(3),WebGPU(1)Test GPU (not a real crash)(4)First report
0.0.0-livetestLive test from Bean-Ops (Linux)Vulkannone (live test)Test GPU (not a real crash)Test CPUCrash
The log before it
[not a release] Crash: 0xc0000005 (read) at
windowtest.exe+0xbea4in0.0.0-windowtestf50e09465c5c· seen 1 time · first 2026-11-13 03:25 UTC · last 2026-11-13 03:25 UTC0.0.0-windowtest(1)Window test from feat/crash-report-window (Arch Linux, Linux 7.3.3)(1)Vulkan(1)Test GPU (not a real crash), RADV 26.0(1)First report
0.0.0-windowtestnoWindow test from feat/crash-report-window (Arch Linux, Linux 7.3.3)VulkanKokiri Forest (child)Test GPU (not a real crash), RADV 26.0Test CPU (not a real crash), 32 GBCrash
The log before it
Settings
[not a release] Crash: 0xc0000005 (read) at
longshot.exe+0x1a2b3cin3.4.1d778f8f4c96c· seen 1 time · first 2026-11-13 03:49 UTC · last 2026-11-13 03:49 UTC3.4.1(1)Windows 11 (build 26100)(1)Vulkan(1)AMD Radeon RX 7800 XT, 26.1.1(1)First report
3.4.1noWindows 11 (build 26100)VulkanKokiri Forest (child)AMD Radeon RX 7800 XT, 26.1.1AMD Ryzen 7 7800X3D (16 threads), 32 GBCrash
The log before it
Settings
[not a release] Crash: 0xc0000005 (read) at
libc.so.6+0xb5a22inv2.1.0-rc.3-347-g5d83b5524d05940b48f1· seen 1 time · first 2026-11-13 04:34 UTC · last 2026-11-13 04:34 UTCv2.1.0-rc.3-347-g5d83b552(1)CachyOS (Linux 7.3.3-1-cachyos), KDE (wayland)(1)not known(1)NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06(1)First report
v2.1.0-rc.3-347-g5d83b552noCachyOS (Linux 7.3.3-1-cachyos), KDE (wayland)not knownNVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06AMD Ryzen 7 6800H with Radeon Graphics (16 threads), 15 GBCrash
The log before it
Settings
[not a release] Crash: 0xc0000005 (read) at
libc.so.6+0xb5a22inv2.1.0-rc.3-348-ge24996da-dirtyf6ea6a6d9923· seen 1 time · first 2026-11-13 04:41 UTC · last 2026-11-13 04:41 UTCv2.1.0-rc.3-348-ge24996da-dirty(1)CachyOS (Linux 7.3.3-1-cachyos), KDE (wayland)(1)not known(1)NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06(1)First report
v2.1.0-rc.3-348-ge24996da-dirtynoCachyOS (Linux 7.3.3-1-cachyos), KDE (wayland)not knownNVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06AMD Ryzen 7 6800H with Radeon Graphics (16 threads), 15 GBCrash
The log before it
Settings
[not a release] Crash: 0xc0000005 (read) at
libc.so.6+0xb5a22inv2.1.0-rc.3-350-g5f2b4e7904405d2efb5f· seen 1 time · first 2026-11-13 04:49 UTC · last 2026-11-13 04:49 UTCv2.1.0-rc.3-350-g5f2b4e79(1)CachyOS (Linux 7.3.3-1-cachyos), KDE (wayland)(1)not known(1)NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06(1)First report
v2.1.0-rc.3-350-g5f2b4e79noCachyOS (Linux 7.3.3-1-cachyos), KDE (wayland)not knownNVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06AMD Ryzen 7 6800H with Radeon Graphics (16 threads), 15 GBCrash
The log before it
Settings
[not a release] Crash: 0xc0000005 (read) at
unknown+0x10inv2.1.0-rc.3-351-g81ce708313cae2a31d9c· seen 3 times · first 2026-11-13 05:11 UTC · last 2026-11-13 06:14 UTCv2.1.0-rc.3-351-g81ce7083(3)Windows 10 (build 19045), Wine 11.21(3)not known(3)NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06(3)First report
v2.1.0-rc.3-351-g81ce7083noWindows 10 (build 19045), Wine 11.21not knownNVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06AMD Ryzen 7 6800H with Radeon Graphics (16 threads), 15 GBCrash
The log before it
Settings
[not a release] Crash: 0xc0000005 (write) at
longshot+0x1a5baf98inv3.0.0-rc.3-105-g6b698e81-dirty9e3deae67c3d· seen 1 time · first 2026-11-15 04:30 UTC · last 2026-11-15 04:30 UTCv3.0.0-rc.3-105-g6b698e81-dirty(1)CachyOS (Linux 7.3.4-1-cachyos), KDE (wayland)(1)Vulkan(1)NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06(1)First report
v3.0.0-rc.3-105-g6b698e81-dirtynoCachyOS (Linux 7.3.4-1-cachyos), KDE (wayland)VulkanTitle and introNVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06AMD Ryzen 7 6800H with Radeon Graphics (16 threads), 15 GBCrash
The log before it
Settings
[not a release] Crash: 0xc0000005 (read) at
mkw.exe+0xa71e57in0.0.0-api-testbfab8c251ffc· seen 4 times · first 2026-11-16 00:10 UTC · last 2026-11-16 00:41 UTC0.0.0-api-test(4)Arch Linux (API test)(4)Vulkan(4)API test GPU(4)First report
0.0.0-api-testnoArch Linux (API test)VulkanAPI test (Claude)API test GPUAPI test CPUCrash
The log before it
[not a release] Crash: 0xc0000005 (write) at
longshot+0x1d935758inv3.0.0-rc.4-163-g36f416e1-dirtya44410cd3fa9· seen 1 time · first 2026-11-16 05:45 UTC · last 2026-11-16 05:45 UTCv3.0.0-rc.4-163-g36f416e1-dirty(1)CachyOS (Linux 7.3.4-1-cachyos), KDE (wayland)(1)not known(1)NVIDIA GeForce RTX 3060 Laptop GPU(1)First report
v3.0.0-rc.4-163-g36f416e1-dirtynoCachyOS (Linux 7.3.4-1-cachyos), KDE (wayland)Preparing shadersNVIDIA GeForce RTX 3060 Laptop GPUAMD Ryzen 7 6800H with Radeon Graphics (16 threads), 15 GBCrash
The log before it
Settings