They've missed the big functionality change in Chrome 17. Everyone knows that Chrome puts each tab in a different process. However that isn't actually true -

They've missed the big functionality change in Chrome 17. Everyone knows that Chrome puts each tab in a different process. However that isn't actually true - if you open a tab from a page (eg middle click, ctrl click) then the tab is opened using the same process as the current page. Those of us who visit HN and Reddit front pages opening lots of links to read later will find all of them sharing the same process. In Chrome 17 they set the maximum memory use for the process to 1GB. As usage approaches that amount the garbage collector runs and will eventually hit 100% CPU time since it will not find anything to free but the process has run out of memory. In Chrome 16 the limit was 2GB which took at least twice the effort to hit, but still was just as annoying. There is no way of fixing this problem I can find (the --process-per-tab option doesn't do it). (You can kill the process and/or reload the browser but that loses state in pages.) I'm on a 64 bit machine with 16GB ram and 8 cpu cores, so having the browser stuck at 6% of my ram and 12% of my cpu is annoying.