Skip to content
The Point of Failure

Episode 13 · Games and Live Services · 2:02

The Fan Who Fixed a Billion Dollar Game

01:40 · Point of failure

For seven years GTA Online could take minutes to load. In 2021 a programmer working without the source code traced most of the wait on his PC to one in-game item list being read inefficiently. Rockstar confirmed it, shipped a fix for the PC version and paid a bounty.

Incident

Topics
games · performance · profiling · scale
Point of failure
Nobody inside had measured where the load time was going, so one in-game item list read inefficiently went unnoticed for seven years.

Transcript

273 words · 1 min read

The ritual

A game made billions of dollars while every player waited six minutes for it to load. Then one anonymous fan fixed it from his bedroom. This is The Point of Failure, episode thirteen.

GTA Online. One of the most profitable entertainment products in history. And for seven years, its players had a shared ritual: press play... and go make tea. The loading screen was a meme. Everyone assumed it had to be that way. Huge game, huge world, long load. Right?

The outsider

In 2021, a programmer going by t0st gets curious. He cannot see the source code, so he does it the hard way: he watches what the game's own processor is doing while it loads. And he finds something absurd. Most of that six minutes is the game reading one list. A ten megabyte list of in game items. Read in just about the least efficient way possible, checking and rechecking the same text over and over.

The patch

He writes a small patch. His load time drops around seventy percent. Six minutes becomes under two. He publishes the findings. And Rockstar does the honorable thing: confirms it, ships an official fix to everyone, and pays him ten thousand dollars. For a bug that lived in a billion dollar product... for seven years.

Nobody measured

Point of failure

Nobody inside had ever measured where the time was going. Millions of players felt the problem every single day. It took one outsider who refused to accept that slow was normal.

Every failure has a story. Every story was preventable. I'm Kevin. See you at the next one.

Sources

8 sources

  1. How I cut GTA Online loading times by 70%

    t0st (nee.lv) · 2021

    The six minute load and the 69.4 percent improvement are the author's measurements on his own PC; the post records faster machines loading in about two minutes.

  2. GTAV Title Update 1.53 Notes (PS4 / Xbox One / PC)

    Rockstar Games Customer Support · 2021

    The 16 March 2021 notes list the loading time improvement under the PC section and thank t0st; the fix shipped to PC players.

  3. Grand Theft Auto V® Worldwide Sales Surpass $1 Billion In First Three Days

    Take-Two Interactive Software, Inc., filed with the U.S. Securities and Exchange Commission (EDGAR, 20 September 2013) · 2013

  4. CREATIVITY INNOVATION EFFICIENCY 2021 ANNUAL REPORT

    Take-Two Interactive Software, Inc. · 2021

    Reports over 145 million units of Grand Theft Auto V sold-in; Take-Two does not publish revenue for a single title.

  5. This violent videogame has made more money than any movie ever

    MarketWatch (archived by the Internet Archive) · 2018

    The six billion dollar figure is MarketWatch's estimate, not a Take-Two disclosure.

  1. 05

    The Video Game Plague That Scientists Still Study

    A World of Warcraft boss attack escaped its dungeon through pets that preserved its state, turned capital cities into a virtual epidemic, and gave epidemiologists an accidental experiment in how people behave when the rules break.

  2. 03

    The Song That Broke YouTube's Math

    Gangnam Style's view count approached the maximum value of a signed 32-bit integer. YouTube widened the counter before it overflowed, a friendly example of a failure mode that is much less friendly in systems that cannot be patched in time.

  3. 15

    The AI That Deleted Production (And Then Lied About It)

    In July 2025 an AI coding agent deleted a live production database during a code freeze, then told the user the data could not be restored. A rollback worked. Replit called the deletion unacceptable, refunded the user and separated development from production databases by default.