Quick answer: PixelArray locks the surface. Delete the array (del pa or pa.close()) before calling blit on the surface. Or use surfarray with numpy, which is faster and handles locks cleanly.

You build a procedural texture by writing pixels to a Surface via PixelArray, then blit the surface. The screen shows the texture’s previous state — or nothing. Your writes happened but aren’t visible. The PixelArray is still alive when you tried to blit.

The Lock

PixelArray obtains a write lock on the surface. While locked:

The fix is to release the lock before drawing.

The Fix

import pygame

surf = pygame.Surface((128, 128))

pa = pygame.PixelArray(surf)
for y in range(128):
    for x in range(128):
        pa[x, y] = (x * 2, y * 2, 0)
del pa   # release the lock

screen.blit(surf, (0, 0))

The del pa destroys the PixelArray instance, releasing the lock. Now the blit reads from a non-locked surface and the writes are visible.

Use a Context Manager

with pygame.PixelArray(surf) as pa:
    for y in range(128):
        for x in range(128):
            pa[x, y] = (x * 2, y * 2, 0)
screen.blit(surf, (0, 0))

The with block releases the lock automatically on exit. Clean and harder to leak.

Faster: surfarray with numpy

PixelArray is slow for bulk edits because every assignment goes through Python. numpy-backed surfarray is much faster:

import numpy as np
import pygame
import pygame.surfarray

surf = pygame.Surface((128, 128))
arr = np.zeros((128, 128, 3), dtype=np.uint8)

# vectorized fill
x_idx = np.arange(128)[:, None]
y_idx = np.arange(128)[None, :]
arr[:, :, 0] = (x_idx * 2).astype(np.uint8)
arr[:, :, 1] = (y_idx * 2).astype(np.uint8)

pygame.surfarray.blit_array(surf, arr)
screen.blit(surf, (0, 0))

Roughly 100× faster for a 128×128 surface and locks handled internally by surfarray.

Per-Pixel Convenience: set_at

For a few pixels — under 1000 — surface.set_at((x, y), color) is the simplest path. It manages its own short-lived lock per call. Don’t use for bulk fills; the per-call overhead is too high.

Verifying

Print surf.get_locks() after your edit code. An empty list means the surface is unlocked and ready to blit. A non-empty list shows a lingering PixelArray reference.

Understanding the issue

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

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

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 Pygame-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 Pygame, 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

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.

“PixelArray writes go through. The lock just prevents you seeing them until released.”

For procedurally generated textures, numpy + surfarray is the only realistic choice — PixelArray is too slow for animation frame rates.