Fix: GameMaker Surface Lost After Window Resize

Here is how to fix GameMaker surface lost after window resize. You create a surface in Create event for a minimap, lighting overlay, or post-processing pass. It works beautifully. Player alt-tabs away and back — the surface is gone, and your draw event throws “surface does not exist” errors. Or the window resizes and the next frame the surface is random noise or pure black. GameMaker surfaces are GPU resources, and GPU resources do not survive OS events reliably.

The Symptom

A surface created in an object’s Create event works for a while, then stops. Triggers that cause the break:

• Alt-tab away from the game and back
• Toggle fullscreen/windowed
• Resize the game window
• Lock the screen and unlock
• Connect an external display

Result is an error about invalid surface, or (worse) the surface reference is still “valid” but contains garbage pixels.

What Causes This

Surfaces are GPU-only. Unlike regular data, surfaces are not kept in RAM. They live in video memory. When the OS needs video memory for something else (another fullscreen app, display mode change, etc.), it can invalidate surfaces. GameMaker’s surface IDs survive but the underlying GPU texture is gone.

Fullscreen toggle recreates the GPU context. Switching between windowed and exclusive fullscreen destroys the current GPU device. All surfaces are invalidated. GameMaker fires the surface_reset event when this happens.

Window resize reallocates backbuffer. On resize, GameMaker resizes the default drawing surface. User-created surfaces of fixed size survive, but their contents may be cleared.

Assuming surfaces persist forever. A surface created in the Create event and never checked for existence again is a bug waiting to trigger. Works for 10 minutes of testing, fails during a 30-minute playthrough when the player tabs out.

The Fix

Step 1: Always check surface_exists before use. In any Draw event that uses a persistent surface:

// Draw event
if (!surface_exists(minimap_surf)) {
    minimap_surf = surface_create(256, 256);
    redraw_minimap = true;
}

if (redraw_minimap) {
    surface_set_target(minimap_surf);
    // redraw the minimap contents
    draw_clear(c_black);
    // ... draw world markers, player icon, etc. ...
    surface_reset_target();
    redraw_minimap = false;
}

// Now it's safe to draw the surface to screen
draw_surface(minimap_surf, 0, 0);

The check runs every frame but only recreates when needed. The redraw_minimap flag ensures the surface is repopulated after recreation — otherwise the first frame after alt-tab shows empty surface.

Step 2: Hook the system event. GameMaker fires an Async System event with event_type == ev_gui or specifically “System Event” with event_id indicating surface reset. Handle it to recreate all surfaces proactively:

// Async - System event
if (async_load[? "event_type"] == "surface_reset") {
    // Recreate every persistent surface
    if (!surface_exists(minimap_surf))
        minimap_surf = surface_create(256, 256);
    if (!surface_exists(lighting_surf))
        lighting_surf = surface_create(room_width, room_height);

    redraw_all = true;
}

Proactive recreation plus reactive checks in Draw covers both cases — explicit surface loss events and unexpected ones.

Step 3: Separate surface for each use. Do not reuse one surface for multiple render targets. If your minimap and lighting overlay share a surface, a resize invalidates both but your code only rebuilds one. Keep them separate so the rebuild is specific.

Step 4: Clean up unused surfaces. Surfaces consume VRAM. Freeing them when not in use reduces the chance of resource pressure triggering invalidations elsewhere. When your object is destroyed, free its surfaces:

// Destroy event
if (surface_exists(minimap_surf))
    surface_free(minimap_surf);

Avoid Dynamic Surface Sizes

Recreating a surface every time the window resizes (to match screen dimensions) is common but wasteful. Pick a fixed surface size that matches your game’s internal resolution (say 1920x1080) and scale it to fit the window when drawing. The surface is stable across resizes.

// Draw GUI event (works in GUI space, fixed coords)
draw_surface_stretched(game_surf, 0, 0,
    display_get_gui_width(), display_get_gui_height());

Debug Logging

Log surface state during suspect events to understand when losses happen:

// Draw event
if (!surface_exists(minimap_surf)) {
    show_debug_message("Surface lost at frame " + string(current_frame));
    minimap_surf = surface_create(256, 256);
}

You can correlate surface losses with game events — alt-tab, resize, etc. Pattern reveals whether it is environmental or triggered by your own code somewhere.

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In GameMaker Studio, 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

Bugs of this class are particularly easy to ship past internal QA because they often depend on specific runtime conditions - hardware combinations, network states, or asset configurations that QA didn't reproduce. Players hit them in the wild, file reports that are hard to repro, and the bug accumulates negative reviews while engineering tries to recreate the failure mode.

At the engine level, the behavior comes from a deliberate design decision in GameMaker. 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

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

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

Live games surface this bug class at scale. What's a rare edge case in development becomes a daily occurrence once you have a few thousand concurrent players. The class isn't 'this player has a unique setup'; it's 'one in N thousand sessions will trigger this exact combination'.

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

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

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 GameMaker-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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

Within GameMaker, 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.

“Never trust a surface to exist. Check every frame. It costs one boolean op and saves you crash reports.”

Related Issues

For general GameMaker fixes, see GameMaker Alarm Not Firing. For broader graphics-resource loss patterns, Unity RenderTexture Memory Leak covers related lifetime issues in a different engine.

surface_exists every frame. Recreate on demand. Surfaces are never permanent.