News for hackers. Stuff that matters.
Re:64-bit Firefox discontinued on Windows by shritesh on Thursday November 22, 2012 @12:49AM (#4817658)
I was really looking forward to the 64-bit version but it never looked as if Mozilla was ever serious about it.
Re:64-bit Firefox discontinued on Windows by shardling on Thursday November 22, 2012 @12:57AM (#4817681)
What was the advantage you saw in it?

From the brief discussion, it sounds like it had inferior performance to the 32 bit builds, and was buggier to boot.

Re:64-bit Firefox discontinued on Windows by shritesh on Thursday November 22, 2012 @01:02AM (#4817693)
Yeah, that was the problem. Downloading from the servers, I tended to choose the x64 version and it was never good. The x86 always have been better.
Re:64-bit Firefox discontinued on Windows by ajryan on Thursday November 22, 2012 @12:53AM (#4817671)
What did you need that only x64 could provide?
Re:64-bit Firefox discontinued on Windows by barrkel on Thursday November 22, 2012 @01:04AM (#4817705)
My desktop has 24GB of RAM, yet Firefox crashes on a regular basis when it bounces off its 2GB limit, usually when many image-heavy pages are opened, especially simultaneously from a folder of bookmarks. Seems like the single simplest thing to fix this is the option of using a 64-bit binary, given that it appears most of the work is already done.

The alternative is to break up the browser into multiple processes, much like Chrome. That would however reduce the distinctiveness of Firefox and be one less reason to keep using it. Though the reliability effects of using multiple processes is probably better in the end.

But sooner or later - sooner if various GL things ever get proper uptake - individual web pages are going to need more than 2GB to display and run. The bullet will need to be bitten, even in a multi-process model.

Re:64-bit Firefox discontinued on Windows by Dylan16807 on Thursday November 22, 2012 @02:43AM (#4817928)
2GB limit? Unless something went wrong on your system firefox should be marked as large address aware and get 4GB.

I'm impressed that you've gotten a browser that big on normal pages. I've only gotten it on ridiculously huge test pages or from memory leaking over time.

Re:64-bit Firefox discontinued on Windows by gryph0n on Thursday November 22, 2012 @04:59AM (#4818181)
I run into the 2G limit very frequently too. I usually shutdown my home & work systems only once a week. Firefox too runs continuously from the 1st day of the week.

Over the duration of a week, as I open more webpages, the virtual memory consumption rises continuously till it hits the 2G limit and then the process kills itself. Usually during the last few hundred MB before the 2G limit, it becomes pretty unresponsive.

I believe you're referring to the linker options for large memory awareness http://msdn.microsoft.com/en-us/library/wz223b1z%28v=vs.80%2...

I'd be glad if as a user (not developer) I can set that option somewhere.

P.S., I am a developer, but over time, you learn that building unfamiliar codebases is not a trivial exercise. On Win32, I'm just happier downloading vendor provided binaries. On Linux, I can be both, happy and frustrated, building my own binaries with Gentoo.

Re:64-bit Firefox discontinued on Windows by barrkel on Thursday November 22, 2012 @02:33PM (#4819762)
Firefox.exe is indeed large address aware (I just checked), but I had never seen it use more than 2GB of address space. It usually hovers around 700M of private memory and 1.5G of address space.

However, I just opened a few image-intensive pages and monitored the process, and got address space up to 2.4G or so. It's been a while (perhaps 6 weeks) since I saw a crash, maybe it's been fixed recently.