Hacker News Reader

Comment by iam | Hacker News Reader

Unfortunately I'm not sure that anyone will bother fixing their sites until everyone else starts doing it too.

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.

If some day in the future there's an extremely easy way to figure out which sites are using how much memory (each tab in a process?) then we could start seeing some push back for JS leaks to be fixed.

View on HN

  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.

If users start complaining about the performance of a site, and memory leaks are the cause, web developers will start fixing memory leaks. It's easy for them to initially say, "it's the browser's fault," but eventually, someone is going to start poking around in the site itself if they get enough complaints.

By the way, I'm not sure what architecture other browsers use, but Chrome already has a separate process for each tab. Under the wrench icon in the far right, if you go to Tools -> Task Manager, you can see the memory used by each tab.

I think that that day is rapidly approaching or here already. Using chrome you can inspect per tab memory usage and use that to identify leaks that may be coming from a page (in fact that's what the author did originally). And in firefox you can use about:memory to inspect per tab JS memory compartments. Its still not always obvious who is to blame (browser or site), but it is becoming very easy to spot this kind of behavior.

For anyone trying this at home: per-compartment memory reporting is a new feature of about:memory in Firefox 7. You'll need a build from the Aurora channel to try it out right now: http://firefox.com/channel

Reply on news.ycombinator.com