Fix: Godot C# Signal Disconnect on Scene Unload

Here is how to fix Godot 4 C# signal connections that produce errors after scene unload, leak references, or fire on already-destroyed objects. C# garbage collection lifetime is independent of Godot’s C++ node tree. The fix is symmetric connect/disconnect plus validity checks.

The Symptom

Connecting a signal works. After scene change or QueueFree, signals fire and you get Cannot resolve method on freed instance errors. Or memory grows over time as connections never disconnect.

What Causes This

C# delegate holds Godot reference. A C# delegate keeps a managed reference to the receiver. After the Node is freed by Godot, the delegate is still in the signal’s connection list.

Asymmetric lifetime. Connect in Ready, never disconnect, scene unloads, signal fires → error.

Lambda captures. Lambdas capturing this hold the receiver alive longer than expected.

The Fix

Step 1: Connect in EnterTree, disconnect in ExitTree.

using Godot;

public partial class Player : Node2D
{
    public override void _EnterTree()
    {
        GameState.Instance.ScoreChanged += OnScoreChanged;
    }

    public override void _ExitTree()
    {
        if (IsInstanceValid(GameState.Instance))
            GameState.Instance.ScoreChanged -= OnScoreChanged;
    }

    private void OnScoreChanged(int score) { GD.Print(score); }
}

Step 2: For one-time events, use ConnectFlags.OneShot.

tween.Finished += OnFinished;   // stays connected

// or one-shot via Connect API
tween.Connect(Tween.SignalName.Finished,
    Callable.From(OnFinished),
    (uint)ConnectFlags.OneShot);

OneShot auto-disconnects after firing once.

Step 3: Guard handlers with IsInstanceValid.

private void OnScoreChanged(int score)
{
    if (!IsInstanceValid(this)) return;   // receiver freed
    // safe to use Node members
}

Step 4: Avoid lambda captures.

// Avoid - lambda holds 'this'
GameState.Instance.ScoreChanged += s => { Label.Text = s.ToString(); };

// Prefer - named method, easy to disconnect
GameState.Instance.ScoreChanged += OnScoreChanged;

Step 5: Use weak signals for autoload connections. Autoloads outlive scenes. Connecting from a scene’s node to an autoload can leak. The OneShot or ExitTree disconnect ensures clean teardown.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Godot Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Godot. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

Diagnostic approach

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

For Godot-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Godot, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Symmetric connect and disconnect. IsInstanceValid for safety. OneShot for one-time. Memory and signals stay clean.”

Related Issues

For GDScript signal disconnects, see Signal Lost After Scene Reload. For C# export build, see C# Export Build.

EnterTree connect, ExitTree disconnect. IsInstanceValid in handlers. No leaks.