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 comi

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.