Quick answer: Do the heavy computation on the thread, then use call_deferred to schedule node mutations so they run safely on the main thread between frames.

Your background Thread computes a result and then calls add_child(node) directly, causing intermittent crashes. Scene-tree mutations must run on the main thread. Here is how to route them safely with call_deferred.

How to fix it

1. Compute on the thread, defer the apply

Keep only data work on the Thread. When ready, call node.call_deferred("add_child", child) so the actual tree change runs on the main thread next idle frame.

2. Defer property writes too

Use set_deferred("position", value) instead of assigning node properties directly from the thread, since even property setters can touch tree-managed state.

3. Join the thread before quitting

Call thread.wait_to_finish() in _exit_tree so a deferred call does not target a freed node during shutdown.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.