What causes calls on a previously freed instance in Godot?

Code kept a reference to a node after queue_free() ran — a signal, timer, lambda, or array entry fired later and called a method on the dead object.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix “Attempt to call function on a previously freed instance” in Godot

Q: How do you fix calls on a previously freed instance in Godot?

Clear or re-check references after freeing: use is_instance_valid() before deferred calls, disconnect signals on teardown, and purge freed entries from arrays each frame.

Quick answer: Clear or re-check references after freeing: use is_instance_valid() before deferred calls, disconnect signals on teardown, and purge freed entries from arrays each frame.

Freeing a node does not free every reference to it — those references now point at a corpse, and calling through them raises this. Here is how to keep dead nodes out of live code paths.

How to fix it

1. Guard the late callers

Timers, tweens, awaited signals, and lambdas that capture a node must check if (not is_instance_valid(target)): return when they finally run.

2. Purge collections on death

Enemy lists, target arrays, and squad members keep freed entries alive as invalid references — remove on a died signal, or filter with is_instance_valid before iterating.

3. Prefer signals' automatic disconnect wisely

Godot disconnects a freed node's own connections, but connections *to* methods of other objects that reference the freed node in captured state still fire — audit lambdas especially.

4. Reproduce with rapid kill/spawn

Spam the spawn-kill cycle in a test scene; use-after-free bugs are timing-dependent and this makes them fire every time.

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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.