Crash a few seconds after loading in (libcef / in-world screens)
The message
This one is not your computer, and there is no setting you can change to avoid it. AGN has televisions and screens placed around the world, and one of them was showing a live stream that the version of the browser built into FiveM cannot play. When your game got close enough to draw that screen, the browser inside FiveM stopped working and took the game with it. Telling staff roughly where you were, or where you spawn, is the single most useful thing you can do, because that is what identifies which screen it was.
What you see
- The game crashes a few seconds after you finish loading in, not during the download
- It happens again on the next attempt, so the server feels impossible to join
- You may never see your character spawn
- It can also happen mid-session on walking into a bar, club or anywhere with screens on the wall
What usually causes it
- The crash is inside libcef - FiveM's embedded browser - rather than in the game. The game did not fault; the browser did
- An in-world screen was tuned to a LIVE STREAMING site. Those sites ship their own low-latency video player built on WebAssembly, which is the specific thing that kills the browser inside FiveM
- Confirmed on AGN Dev on 2026-10-15: a public screen pointed at a Kick channel, which runs on Amazon IVS - the same decoder already proven to crash the client when Twitch was tested
- Screens only render within about 35m, so the crash follows WHERE you spawn or walk rather than what you do
Worth checking first
- Ask what was on screen, or what the player was walking past or towards, in the seconds before it happened
- Establish whether it happens at the same place every time - a fixed location points straight at a placed screen
- Check whether it happens within a few seconds of load-in specifically, rather than at a random moment
- Ask whether other players in the same venue crashed too
Safe steps, one at a time
- There is nothing the player can change in their settings that fixes this. It is a server-side screen, and the fix is to stop that screen playing that address
- Collect the crash report and the FiveM log and pass them to the developers with this entry's id
- If the player can say roughly where they were, say so in the ticket - the location is what identifies the screen
These are suggestions, not instructions. Do only what you are comfortable with, back up anything important first, and stop if a step does not match what is on your screen. Advice, risk and responsibility.
When to stop and ask staff
Escalate to developers. This is an AGN screen configuration problem and no player-side change fixes it. Treat it as urgent if more than one player reports being unable to join, because a screen near a spawn point crashes everybody who loads in near it.
Looks like
AGN server
What staff will need
- The crash report ZIP or the FiveM log containing the libcef line
- Roughly where the player was in the world, or where they spawned
- Whether it happened just after loading in or later in the session
- Whether anybody else crashed at the same time or in the same place
Applies to
Independent of the player's hardware, drivers and settings. Unrelated to VRAM. YouTube, direct video files, images and ordinary web pages on screens are unaffected - it is live-stream players specifically.
Last reviewed Thu Oct 15.