Skip to main content

Firefox Builds 'Too Big' for Developers Working on 32-Bit Windows

Even though various reports claim that Firefox's SpiderMonkey JavaScript engine might be on some "memory diet," the recent Firefox builds are too "huge for the developers to work upon" on the 32-bit version of Windows. And the space constraints have resulted in various problems.

The root of the problem is the 3GB virtual address space limit present in the 32-bit Windows. Mozilla developer, Kyle Huey, commented in an email that , "The problem seems to be that the linker is running out of virtual address space during the optimisation phase." This email was posted on Google Groups.

The problem, Huey stated, is that until a permanent solution is discovered, the team has, "turned off or ripped out a few new pieces of code (Graphite, SPDY, libreg) which has brought us back down under the limit for the moment."

For the record, this is not the first time Firefox faced this problem. A similar incident happened in the beginning of 2010. At that time, the 2GB limit problem was resolved via changing the 3GB switch. However, this time, unfortunately, the options to solve the problem are not that easy, said the developer.