News for hackers. Stuff that matters.
Re:64-bit Firefox for Windows should be prioritized, not sus... by mh- on Tuesday November 27, 2012 @03:29AM (#4836226)
>Address space shortage will likely be covered by the tab unloading feature mentioned in the article, before it becomes an issue in practice.

before? I've seen Firefox run up against the 2gb limit[1] for years.

This 4GB space is evenly divided into two parts, with 2GB dedicated for kernel usage, and 2GB left for application usage. Each application gets its own 2GB, but all applications have to share the same 2GB kernel space.

[1]: http://www.brianmadden.com/blogs/brianmadden/archive/2004/02...

Re:64-bit Firefox for Windows should be prioritized, not sus... by masklinn on Tuesday November 27, 2012 @04:32AM (#4836384)
Firefox runs in 3GB, so it leaves 1GB for the kernel and uses 3GB for itself.
Re:64-bit Firefox for Windows should be prioritized, not sus... by ygra on Tuesday November 27, 2012 @05:38AM (#4836560)
Only if you enable the 3GB switch for Windows. Or on 64-bit Windows where FF gets 4 GiB, then.
Re:64-bit Firefox for Windows should be prioritized, not sus... by potkor on Tuesday November 27, 2012 @05:51AM (#4836581)
32-bit Windows (with the 2GB limit) couldn't run the 64-bit Firefox in any case, so in the context of this discussion the 32-bit build is always getting 4GB of address space.