Why do my signal connections break after change_scene_to_file?

change_scene_to_file frees the current scene tree. Any nodes inside that scene are deleted, including their signal connections. If your old scene connected to an autoload signal, the autoload still has the connection record but the receiver is invalid, leading to errors when the signal fires.

How do I reconnect signals safely after a scene reload?

Connect signals in _ready of the new scene's nodes. _ready runs after the new scene tree is fully loaded, ensuring receivers exist. Use connect with CONNECT_ONE_SHOT for events that should auto-disconnect, or check is_connected before reconnecting to avoid duplicates.

Why does my autoload emit signals to deleted nodes?

Autoloads survive scene changes; their connection lists are not cleared automatically when receiving nodes are freed. Always disconnect signals in _exit_tree on the receiver, or connect with the CONNECT_REFERENCE_COUNTED flag so connections clean themselves up.

Fix: Godot Signal Connection Lost After Scene Reload

Quick answer: change_scene_to_file frees the current tree. Any signal connections from autoloads to nodes inside that tree become stale. Reconnect signals in _ready of the new scene’s nodes, and disconnect them in _exit_tree. For ergonomics, connect with CONNECT_REFERENCE_COUNTED.

Here is how to fix Godot signal connections that disappear after a scene change. Your main menu connects an autoload event to a UI label. The user clicks Play, the scene swaps, and a few seconds later you get Attempt to call function 'on_score_changed' in base 'previously freed object'. Or worse, no error — the signal just stops updating the UI because the receiver no longer exists.

The Symptom

You connect a signal once in _ready and it works. After calling get_tree().change_scene_to_file, signals from autoloads no longer reach handlers in the new scene. Or signals continue firing but produce errors mentioning “previously freed object”. Reloading the same scene with get_tree().reload_current_scene shows the same problem.

What Causes This

Receivers freed without disconnect. When a scene changes, all its nodes are freed. Their signal connections to long-lived emitters (autoloads, parent nodes) remain in the emitter’s list. The next emit walks those records and calls into freed memory.

New scene does not reconnect. The new scene’s nodes do not automatically inherit the previous scene’s signal connections. Each new _ready must establish its own.

Duplicate connections on reload. If you connect in _ready without checking is_connected, repeated reloads can stack multiple connections, causing handlers to fire multiple times per emit.

Lambda captures. A lambda passed to connect can hold references to local variables. When those references go stale, lambda invocations fail unpredictably.

The Fix

Step 1: Connect in _ready and disconnect in _exit_tree.

extends Label

func _ready():
    GameState.score_changed.connect(_on_score_changed)
    _on_score_changed(GameState.score)

func _exit_tree():
    if GameState.score_changed.is_connected(_on_score_changed):
        GameState.score_changed.disconnect(_on_score_changed)

func _on_score_changed(value: int):
    text = "Score: %d" % value

This guarantees clean teardown when the scene unloads, leaving the autoload with no stale records.

Step 2: Use CONNECT_REFERENCE_COUNTED for automatic cleanup.

func _ready():
    GameState.score_changed.connect(
        _on_score_changed,
        CONNECT_REFERENCE_COUNTED
    )

Reference-counted connections automatically disconnect when the receiver object is freed. Combined with is_connected guards, this prevents stacking on reload.

Step 3: Guard against duplicate connections.

func _ready():
    if not GameState.score_changed.is_connected(_on_score_changed):
        GameState.score_changed.connect(_on_score_changed)

Step 4: Avoid lambdas for long-lived connections. Use named methods so you can disconnect them precisely.

# Avoid - lambdas are hard to disconnect
GameState.score_changed.connect(func(v): label.text = str(v))

# Prefer - named method
GameState.score_changed.connect(_on_score_changed)

Step 5: For nodes nested in scenes, prefer signals from immediate parents. Connecting from a leaf node directly to an autoload is fragile. Have the leaf emit its own signal, the parent re-emit, and the autoload subscribe to the parent. Lifetime management becomes simpler.

Detecting Stale Connections

Add a one-shot debug print in your autoload right before each emit:

func change_score(value: int):
    score = value
    for conn in score_changed.get_connections():
        if not is_instance_valid(conn["callable"].get_object()):
            push_warning("Stale connection on score_changed")
    score_changed.emit(value)

If you see warnings, you have an unclean disconnect somewhere. Add _exit_tree handlers to the offending receivers.

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

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

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

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

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

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

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

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

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

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

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.

“Connect in _ready, disconnect in _exit_tree, or use CONNECT_REFERENCE_COUNTED. Pick a strategy and apply it everywhere.”

Related Issues

For autoload visibility issues, see Autoload Not Accessible. For preload null returns, see Preload Not Finding Nested Resource.

Connect in ready. Disconnect in exit. Or let reference counting do it for you.