Wednesday, December 14, 2011

Firefox, seems to be getting a little Bloated.

What the hell are they doing that take up 3GB?  Linking in embedded video streams to the Object code?

I was just looking at an Entire Windowing GUI environment designed for viewing large data sets that would stream data for viewing on a DOS PC (Non Windows) written in 1988 and it's only 200KB done in Turbo Pascal. 

http://developers.slashdot.org/story/11/12/14/1725205/firefox-too-big-to-link-on-32-bit-windows

Firefox Too Big To Link On 32-bit Windows

Posted  on Wednesday December 14, @12:43PM 

An anonymous reader writes"Firefox has gotten so large that it cannot be compiled with PGO on a 32-bit linker anymore, due to the virtual memory limitation of 3 GB. This problem had happened last year with 2 GB, which was worked around by adding a/3GB switch to the Windows build servers. Now the problem is back, and things aren't quite that simple anymore."This only affects the inbound branch, but from the looks of it new code is no longer being accepted until they can trim things from the build to make it work again. The long term solution is to build the 32-bit binaries on a 64-bit system.

1 comment:

teacup said...

It's a design error. Trying to make the browser one giant scripting engine is a mistake. How will they back out?