Heatmap black or frozen: “Graphics context lost” or “Rendering has been stopped”

What you see

The liquidity map is black or stuck while bubbles, lines or the status bar may still look alive, and a banner reads either “Graphics context lost: the liquidity map is no longer being drawn. Reopen the page or restart the app.” or “Rendering has been stopped for {seconds}s while the feed is live: what is left on screen is a frozen image, not the market.”

Why it happens

The heatmap counts cumulative paints and cumulative books received every 250 ms, because a frames-per-second average can keep showing a reassuring value on a frozen image. When the WebGL context reports it was lost, drawing commands become silent no-ops and the map never returns alone. When books keep arriving but paints stop, the painting loop has stopped; since the WebGL canvas is cleared by the compositor after each frame while the 2D overlay keeps its last image, the result looks half-alive.

Graphics drivers can drop a WebGL context under memory pressure, after sleep, or when many GPU-heavy windows are open.

How to fix it

• Leave the Heatmap page and open it again; for a detached window, close and reopen it.
• If the context is lost again, restart the app.
• Reduce GPU load: close other heatmap windows or tiles, or choose the Performance mode in Settings → Performance.
• Update your graphics driver if losses repeat after sleep or screen changes.

What it is not

• Not an empty market: the banner exists so a black map is not read as absent liquidity.
• Not a data outage when the banner says the feed is live.
• Not the start-up failure “The heatmap could not start”, which is a different case.

When to contact support

If the problem persists, contact support through Menu → Report a problem, or on the Senzoukria Discord. Turn on “Diagnostic HUD” in the heatmap settings (it adds FPS, frame errors and re-centrings) and copy those numbers with your GPU model.