On 32-bit Windows, processes have maximum address space limitations which can be easily hit by web browsers. Having more content processes makes it less likely that any particular one will hit that limit. Note that content process OOM crashes are the #1 source of crash reports Firefox gets (and you can see plenty of other OOM crashes in that list further down too):
Oh, so you mean that on 32-bit Windows, processes (can) have an address space that is smaller than the sum of physical RAM + page file? I didn't know that.
On any 32-bit OS, processes have at most 4GB of address space, because that's how much you can address with 32 bits.
In practice some of that is reserved for the kernel, so you get less for use by the process itself. Historically 2GB on Windows, though there were some non-default compilation/linking options you could set to get 3GB.
A 32-bit process running on a 64-bit kernel can get 4GB of address space.
And yes, lots of computers have >4GB physical RAM, even if you don't count swap/page files.
https://crash-stats.mozilla.com/topcrashers/?product=Firefox...