[bzbarsky]

> I have a lot of memory

Not to do process-per-tab and 500 tabs. Each browser process is several tens of megabytes, somewhat unavoidably (that's assuming you do some sort of embryonic startup and then forking so const non-relocatable data can be shared; if you don't it's a lot more). So on pretty much any consumer hardware you would be constantly swapping at best.

Which is why there is not a single browser that does process-per-tab. Chrome certainly doesn't: once you have more than a few tabs they start multiplexing them across processes.