Game: the crash report's graphics card has no driver, and no renderer when the crash is during the start-up shader preparation #1263

Open
opened 2026-11-16 23:27:14 +00:00 by mooki · 1 comment
Member

Longshot version

main at 17394b7111 (the merge of #983). The files involved are unchanged on main 2547a8f3dd.

Channel

Built from source

What kind of problem

Something else

What happened

Two fields of the crash report that Report automatically (and Send crash reports automatically) posts are missing what the description and the docs say they hold.

  1. gpu has no driver. build_report puts f->gpu in the JSON (
    put_field(json, ",\n ", "gpu", f->gpu, HOS_CRASH_MAX_GPU, s, devices, nd);
    ). That is the device name from the vk: <name>, Vulkan ... line. The driver (f->driver, from vk: driver:) is joined to it only for the manual report (line 1059). The report: gpu line, which the renderer writes for this purpose (gpu/vk/vk_main.cpp line 1662) and which carries the name and the driver, is never read: hos_crash_log_line takes report: os, cpu and renderer (
    if ((at = strstr(line, "] report: os "))) hos_crash_take(f->os, sizeof f->os, at + 13);
    ). The old Python reporter in #141 did read it (its test asserts AMD Radeon RX 7800 XT, RADV 26.0).
  2. renderer is not known for a crash during the start-up shader preparation. report: renderer Vulkan is logged only after the back end's start() returns (host/rx_backend.c line 392), and the preparation runs inside start() (started_up() in gpu/vk/vk_main.cpp).

How I know:

  • The test helper, fed a log with vk: NVIDIA GeForce RTX 3090, Vulkan 1.4, ...; mesh shaders yes, vk: driver: NVIDIA 580.95.05 and report: gpu NVIDIA GeForce RTX 3090, NVIDIA 580.95.05, posts "gpu": "NVIDIA GeForce RTX 3090".
  • The newest crash comment on issue 81, #81 (comment), lists the GPU as NVIDIA GeForce RTX 3060 Laptop GPU with no driver, map Preparing shaders and renderer not known. The earlier ones (from the Python reporter, for example #81 (comment)) have ..., NVIDIA 620.70.06, so the same card is now two different gpu values in Prometheus. The log folded into that comment has vk: driver: NVIDIA 620.70.06 and report: gpu NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06, and no report: renderer line.
  • tests/test_crash_dialog.py checks the posted field names (line 1003) but not the value of gpu.

Why it matters: the driver is the first thing a GPU crash is split by, issue 81's plan asks for it, the bot's table says "Graphics card and driver", and crashes in the start stage are a common report.

Where in the game

The crash window: Report automatically, or the launcher's Send crash reports automatically.

How often

Every time

Graphics card and driver version

Any. Seen on an RTX 3060 Laptop GPU (NVIDIA 620.70.06) in the live comment, and reproduced with a test log for an RTX 3090 (NVIDIA 580.95.05). Nothing here depends on the card.

CPU, RAM and operating system

Linux; the code is the same on Windows.

Changes from the defaults

None.

longshot_log.txt

Not attached: read from the code, from the existing game-free test helper, and from the public comment above.

Screenshots or video

Not applicable.

What would fix it

  • Read report: gpu in hos_crash_log_line into the GPU field (fall back to the device name plus vk: driver: when it is missing), and assert the posted gpu in the send test of tests/test_crash_dialog.py.
  • Log report: renderer when the back end is chosen, before start(), so a start-stage crash has one.
  • Optional, and better for the data: send the driver as its own driver field, as the performance summary does, so the relay can cut it to major.minor and class it the same way for both streams (the relay ignores fields it does not know, so the game can ship first).

Before you send it

  • The problem is still there on the newest release or nightly (main).
  • I searched the open issues for it.
  • I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
### Longshot version main at 17394b71111f8b7d9d6ecc65f430175145394743 (the merge of https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/983). The files involved are unchanged on main 2547a8f3dd3267be6612bbc1edd79196093a10c4. ### Channel Built from source ### What kind of problem Something else ### What happened Two fields of the crash report that Report automatically (and Send crash reports automatically) posts are missing what the description and the docs say they hold. 1. **`gpu` has no driver.** `build_report` puts `f->gpu` in the JSON (https://git.magicbean.dev/MagicBeanDev/Longshot/src/commit/17394b71111f8b7d9d6ecc65f430175145394743/host/hos_crash_dialog.c#L1291). That is the device name from the `vk: <name>, Vulkan ...` line. The driver (`f->driver`, from `vk: driver:`) is joined to it only for the manual report (line 1059). The `report: gpu` line, which the renderer writes for this purpose (`gpu/vk/vk_main.cpp` line 1662) and which carries the name and the driver, is never read: `hos_crash_log_line` takes `report: os`, `cpu` and `renderer` (https://git.magicbean.dev/MagicBeanDev/Longshot/src/commit/17394b71111f8b7d9d6ecc65f430175145394743/host/hos_crash_dialog.h#L319). The old Python reporter in https://git.magicbean.dev/MagicBeanDev/Longshot/pulls/141 did read it (its test asserts `AMD Radeon RX 7800 XT, RADV 26.0`). 2. **`renderer` is `not known` for a crash during the start-up shader preparation.** `report: renderer Vulkan` is logged only after the back end's `start()` returns (`host/rx_backend.c` line 392), and the preparation runs inside `start()` (`started_up()` in `gpu/vk/vk_main.cpp`). How I know: - The test helper, fed a log with `vk: NVIDIA GeForce RTX 3090, Vulkan 1.4, ...; mesh shaders yes`, `vk: driver: NVIDIA 580.95.05` and `report: gpu NVIDIA GeForce RTX 3090, NVIDIA 580.95.05`, posts `"gpu": "NVIDIA GeForce RTX 3090"`. - The newest crash comment on issue 81, https://git.magicbean.dev/MagicBeanDev/Longshot/issues/81#issuecomment-33797, lists the GPU as `NVIDIA GeForce RTX 3060 Laptop GPU` with no driver, map `Preparing shaders` and renderer `not known`. The earlier ones (from the Python reporter, for example https://git.magicbean.dev/MagicBeanDev/Longshot/issues/81#issuecomment-22651) have `..., NVIDIA 620.70.06`, so the same card is now two different `gpu` values in Prometheus. The log folded into that comment has `vk: driver: NVIDIA 620.70.06` and `report: gpu NVIDIA GeForce RTX 3060 Laptop GPU, NVIDIA 620.70.06`, and no `report: renderer` line. - `tests/test_crash_dialog.py` checks the posted field names (line 1003) but not the value of `gpu`. Why it matters: the driver is the first thing a GPU crash is split by, issue 81's plan asks for it, the bot's table says "Graphics card and driver", and crashes in the start stage are a common report. ### Where in the game The crash window: Report automatically, or the launcher's Send crash reports automatically. ### How often Every time ### Graphics card and driver version Any. Seen on an RTX 3060 Laptop GPU (NVIDIA 620.70.06) in the live comment, and reproduced with a test log for an RTX 3090 (NVIDIA 580.95.05). Nothing here depends on the card. ### CPU, RAM and operating system Linux; the code is the same on Windows. ### Changes from the defaults None. ### longshot_log.txt Not attached: read from the code, from the existing game-free test helper, and from the public comment above. ### Screenshots or video Not applicable. ### What would fix it - Read `report: gpu` in `hos_crash_log_line` into the GPU field (fall back to the device name plus `vk: driver:` when it is missing), and assert the posted `gpu` in the send test of `tests/test_crash_dialog.py`. - Log `report: renderer` when the back end is chosen, before `start()`, so a start-stage crash has one. - Optional, and better for the data: send the driver as its own `driver` field, as the performance summary does, so the relay can cut it to major.minor and class it the same way for both streams (the relay ignores fields it does not know, so the game can ship first). ### Before you send it - [x] The problem is still there on the newest release or nightly (main). - [x] I searched the open issues for it. - [x] I'm not attaching game files, keys, the game's executable, its .bin caches or saves.
Collaborator

Possibly related, for context:

  • #81 feat: crash reports sent from the game to a bot (with consent) — The existing crash-report feature is the context for these reported field inaccuracies; its comments include examples of missing renderer data during startup.
Possibly related, for context: - #81 feat: crash reports sent from the game to a bot (with consent) — The existing crash-report feature is the context for these reported field inaccuracies; its comments include examples of missing renderer data during startup.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#1263
No description provided.