Episode Details
Back to Episodes
Crashes Don't Care What Language You Wrote Your Game In (godotfest2026)
Published 1 week, 6 days ago
Description
A Godot game is rarely written in just one language. You've got GDScript for gameplay, more and more C#/.NET for the heavier systems, and native C++ through GDExtension underneath. Then you export the whole thing to Windows, Linux, macOS, Android, iOS, the Web, SteamOS/Proton, and - for some of us - consoles.
Every one of those languages fails differently. Every one of those platforms reports and symbolicates crashes differently. So when a player hits a bug you can't reproduce, the problem is collapsing that entire grid of languages and platforms into one readable issue, no matter what threw it or where it died.
This talk walks through that problem end-to-end, using Sentry's Godot SDK - recently expanded with first-class .NET support - as the example. We'll look at how a GDScript error, a C# exception, and a native crash differ; how the same crash has to survive Android tombstones, WASM in the browser, and the Proton translation layer on SteamOS; and how you can still get all of it back as a single, grouped, source-mapped issue. It's a talk about the messy reality of shipping a Godot game everywhere at once - and how to stay sane while doing it.
**You write in three languages and ship to eight platforms. A crash can come from any cell in that grid. You need to turn that grid back into one clear answer.**
Most crash-reporting talks assume one language and one platform. Godot oftenbreaks both assumptions at the same time, which is exactly what makes it relevant for all Godot developers,whether they're all-in on GDScript, betting on C#, or dropping into native code for performance.
## Axis 1 - The languages: three ways a game can fail
Under one engine, "an error" means three different things:
* **GDScript** - Errors come from the engine's own script VM. You want the script, the line, and the game state around it, captured live as the game runs.
* **C#/.NET - The newest and fastest-growing surface.** These are managed-runtime exceptions with their own stack shape, and the SDK now captures them as first-class events (including script context and variable values on the platforms that support it). Godot's C# community has been waiting on solid tooling here, which is a big part of why this talk is timely. There's even a build-time check that nudges C# developers toward the Godot-aware SDK instead of the raw one, a small thing that prevents a lot of misconfigured setups.
* **Native / GDExtension (C++)** - When your own native module or the engine itself crashes, you don't get an exception at all; you get a full-process minidump from an out-of-process handler. A completely different capture model from the two above.
The point for the audience: these aren't three flavors of the same thing. They fail differently, they carry different context, and unifying them means agreeing on what an event even is before you can put them together in one list.
## Axis 2 - The platforms: the same crash, eight hostile environments
Now take any of those failures and ship it across Godot's export targets. Each one has different rules:
* **Desktop** (Windows / Linux / macOS) - the baseline, and even here you're juggling different symbol formats and, on Apple, a separate underlying SDK.
* **Android** - its own crash world: tombstones, ANRs ("Application Not Responding"), app hangs, and multiple CPU architectures to build and symbolicate for.
* **iOS** - managed through the platform's native tooling, with its own signing and symbol quirks.
* **Web (WASM)** - your game is now running in a browser sandbox; a crash looks nothing like it does on desktop.
* **SteamOS / Proton** - your Windows build running through a translation layer on Linux. When it crashes, which stack are you even looking at? One example: under Wine the thread's stack bounds can report back wrong, so the crash handler tries to capture a wildly oversized stack - the SDK has to detect that it's running under Proton and rein the capture back in.
* **Consoles** - locked-down platforms where you can'