The web app crashes mid-game ("Array buffer allocation failed")

On the browser version of the game (WebGL), the game may suddenly close mid-session, sometimes with an error message such as « Array buffer allocation failed » or « allocation failed ».

The messages you may see, depending on your browser: "An error occurred running the Unity content on this page. See your browser JavaScript console for more info. The error was : RangeError: Array buffer allocation failed at new ArrayBuffer", or "Array buffer allocation failed at new Uint8Array", or a mention of "Object.expandFileStorage". These are three wordings of the same memory problem.

Two clues that confirm the diagnosis. The error often happens as you zoom on the map, because that is when the game asks for a large chunk of memory at once. And it does not happen on phones or tablets: if the game works on your mobile but not on your computer, it is neither your account nor the race, it really is this browser limit.

What it means

The game runs in your browser using a technology called WebGL, which needs to reserve a single continuous block of memory to work. When available memory is saturated or fragmented (very long session, many open tabs, memory-heavy extensions), the browser can no longer reserve that block and the game stops. This is not related to your account or to the race : it is a technical limit of the browser version.

Solutions, from simplest to most thorough

1. Reload the page with a forced cache clear : Cmd + Shift + R (Mac) or Ctrl + Shift + R (Windows). This starts fresh on clean memory and resolves the issue in most cases.
2. Close your other tabs before starting a race, to free up memory.
3. Fully quit and restart your browser (not just the tab) if the error comes back.
4. Try private/incognito mode or with extensions disabled : some extensions use a lot of memory.
5. Make sure your browser is up to date (see the article « the article The game will not start, or displays badly »).

The most comfortable option for long sessions

The mobile app (iOS and Android) is not affected by this limit. For long sessions, it remains the most stable option.

If the problem persists after all these steps, contact support and include your operating system, your browser and its version.