What causes a GameMaker HTML5 game freezing when the tab is hidden?

The browser throttles the game loop when the tab is hidden, so timers stop advancing and audio may suspend, and the game does not cleanly resume on focus return.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a GameMaker HTML5 Game Freezing When the Tab Is Hidden

Quick answer: Use the Async - Web or focus events to pause gameplay deliberately on blur and resume audio and the loop on focus, instead of relying on the throttled loop.

Switch away from your GameMaker HTML5 game and back, and it sits frozen or with no sound. The browser throttled the loop and suspended audio. Handle blur and focus explicitly so the game pauses and resumes cleanly.

How to fix it

1. Pause deliberately on blur

Detect the tab losing visibility and pause your gameplay state so the throttled loop does not leave the game in a half-updated, frozen-looking condition.

2. Resume audio on focus

On focus return, restart or resume music and the audio system, since browsers suspend the audio context for hidden tabs and may not auto-resume.

3. Clamp catch-up time

Avoid applying a large accumulated delta on the first frame back; treat the resume as a fresh frame so nothing lurches forward.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every GameMaker error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.