The current round of multi-process architectures (that is: Chrome) don't really scale though. After you have so many renderer processes they start shoving unrel

The current round of multi-process architectures (that is: Chrome) don't really scale though. After you have so many renderer processes they start shoving unrelated pages together, so if you short-lived heap-fragmenting pages bundled into the process of a long-lived page then you lose your memory "forever", even when you close the short-lived bad tag. I wonder if you could keep every page in its own process, but manually freeze unused processes and write them out to disk -- an application driven disk paging system basically. For pages where there's no state the browser could just kill them and reload them, iOS style (though the iOS browser doesn't care if it nukes state).