[tbrownaw]

I thought some browsers already do this? But it still won't make use of more than a very small number of cores, one (or a couple) for the tab you're interacting with, and a small part of another one for all the other tabs that are sitting there idle.

[mistercow]

Chrome does split pages across different processes, and this, as far as I know, makes use of multiple cores. For (I assume) memory overhead reasons, it doesn't put each tab in a separate process by default, although there is (or used to be) a flag to switch to that behavior.