4 ms·

Maybe I'm dense but I can't figure out what kind of bug the OP is claiming is acting up here. Does Chrome just sometimes decide to send hundreds of HTTP GET req

Maybe I'm dense but I can't figure out what kind of bug the OP is claiming is acting up here. Does Chrome just sometimes decide to send hundreds of HTTP GET requests for no reason? Is it attempting to pipeline per the HTTP spec and just screwing up? This article is so high on rant and low on information I can't tell what's going on. Have you checked if there's a bug report or filed one yourself?

pyre 16y ago
Sounds like he has an ungodly amount of tabs open and Chrome isn't smart enough to say, "Hey, I have 50+ tabs open on the same website, maybe I shouldn't try to refresh all of them at the same time."
- re 16y ago
  But why refresh them at all? Once a page is open in a background tab, surely Chrome won't just refresh it in a loop for the hell of it?