It's too easy for the web developers to just point the memory leak blame to the browser and none of the users will be the wiser. To be fair, there was a tim

It's too easy for the web developers to just point the memory leak blame to the browser and none of the users will be the wiser. To be fair, there was a time (not so long ago) when browsers leaked obscene amounts of memory routinely. I'm talking about multi-gigabyte Firefox instances with no open windows at all. At the time, browser devs liked to announce either how this was absolutely nothing to be concerned about or how this behavior was a complete figment of the observer's imagination. As a result, web devs stopped caring about browser memory consumption, mainly because they were actively discouraged ("nothing to see here, move along") and personally frustrated about omnipresent leaky behavior they could do nothing against. Nowadays, garbage collection in behaves much better. Even though browsers possibly consume more monstrous amounts of memory than ever before, they tend to give much of it back when the corresponding pages are closed. It's time to bring web devs back to the same table they were told to stay away from only a few years ago. But don't be surprised if this takes a bit longer.