backtop


Print 66 comment(s) - last by mindless1.. on Nov 29 at 3:31 AM

Decision leaves Opera and Microsoft with the only 64-bit browsers, though Google will soon join the pack

Fans of the non-profit Mozilla Foundation have waited... and waited... and waited more still, for Mozilla's popular Firefox browser to add 64-bit support.  With pickup of 64-bit SKUs of Microsoft Corp.'s (MSFT) Windows operating system rapidly accelerating, it certainly seemed a 64-bit browser would be just around the corner.

Instead Mozilla has made the curious decision to pull the plug on the long-delayed project, while offering only small clues as to why the decision was made.

The announcement was posted by Mozilla Engineering Manager Benjamin Smedberg on the Bugzilla development page.  He ordered Mozilla employees and community developers:

Please stop building windows 64 builds and tests.

As for why the he opted to pull the plug on 64-bit for now, he comments, "Many plugins are not available in 64-bit versions.  The plugins that are available don’t work correctly in Firefox because we haven’t implemented things like windowproc hooking, which means that hangs are more common."

Firefox laptop
Firefox 64-bit development is dead for now. [Image Source: Flickr/dimnikolov]

Mozilla may soon find itself in lonely territory.

With Oracle Corp.'s (ORCL) Java and Adobe Systems Inc.'s (ADBE) Flash now supporting 64-bit Windows plug-ins, both Microsoft's Internet Explorer 10 and Opera Software ASA (OSE:OPERA) have made the leap to 64-bit.  Meanwhile Google Inc.'s (GOOG) Chrome, one of the most popular browsers due to its clean UI and strong GPU acceleration, has added 64-bit support in Linux and is in the process of porting its changes to Windows.

In other words, soon Mozilla may be the only browser maker without a 64-bit browser.

Of course, Windows compatibility libraries ensure 32-bit applications (like Firefox) can still run on 64-bit Windows.  But there is a small performance penalty associated.

For that reason one has to wonder whether Mozilla might come to regret its decision to halt development, even if it is only a temporary one.

Source: Bugzilla



Comments     Threshold


This article is over a month old, voting and posting comments is disabled

RE: No big deal, 64-bit browsers are useless
By mindless1 on 11/22/2012 9:52:40 PM , Rating: 3
UNLESS you really, REALLY like to use some of the add-ons that have memory leaks.

Right now I have only 11 tabs open in 4 FF windows, with FF using over 400MB of memory. If I keep only this # of tabs open it will eventually climb to roughly 1GB, within a few hours at most.

We can't fault Firefox dev. team for that, but it is a reality that one of the things that makes the browser so great, the add-ons, is also a potential source of high memory utilization.


RE: No big deal, 64-bit browsers are useless
By Taft12 on 11/23/2012 3:33:14 PM , Rating: 1
Can we call this the Adobe memory tax?


By Trisped on 11/24/2012 4:31:17 PM , Rating: 2
I have not found Adobe plugins to leak memory.

Usually this is the result of a free plugin which does not properly clean up after itself.

In any event, if leaving a page open for 1 hour results in the use of more RAM you will probably benefit from finding the plugin which is leaking (Adobe or otherwise) and disable it.

Note: some change in memory usage is normal, like if ads are updated every 15 minutes, or you are watching a video. Simple, static pages should not have these issues, so if you are sitting at Google's home page and the memory usage keeps climbing then you have a problem which should be fixed.


RE: No big deal, 64-bit browsers are useless
By zzynko on 11/23/2012 9:13:40 PM , Rating: 2
It would seem that your choice of add-ons is rather the question, isn't it.

As of Tuesday when I restarted the computer due to windows updates, I have had an average of over 20 to 30 tabs open at any one time on Firefox Nightly 19.0a1 with about 12 add-ons running. It is using around 500MB right now with 22 tabs open, ranging from heavy flash to plain HTML. So, excuse me if I don't agree with your opinion, I've yet to see a session getting close to what you describe (1GB) in the recent past.

Since I've been running (Minefield) Nightly almost exclusively since the flash support arrived, I had only one instance when it neared the 1GB (890MB with 14 tabs open) mark and it was in the early days of (flaky) 64bit flash development.

The preference of Firefox Nightly usage on a daily basis compared other browsers haven't precluded me from initiating others sessions in IE9 64bit, but it takes me longer to accomplish the same task in it. Chrome becomes wobbly (unresponsive/crashing) with 10 to 12 tabs open and uses more resources than Nightly with twice the amount of tabs open.


By mindless1 on 11/29/2012 3:31:53 AM , Rating: 1
But you're not getting my point, that I'd MUCH rather pay money to increase memory in the system than do without the FF add-ons, they are central to my use of that particular system and at this point I'd just stay off the internet before I'd surf what are today sites so obnoxious that it is intolerable without some add-ons and I don't mean only the two most popular nor that it has anything to do with broadband bandwidth, I just despise some of the asshole ideas put out there these days.


By Argon18 on 11/26/2012 12:00:17 PM , Rating: 2
Adobe plugins do generally suck, with their closed proprietaryness that nobody but Adobe can fix.

But quite frankly, when today you can buy 16 GB of RAM for under $60, is a few hundred megabytes of utilization really that much of a concern? I agree that code efficiency has plummeted in recent years, but with tens of GB of memory in consumer desktop PC's, I can see how nobody cares.


"You can bet that Sony built a long-term business plan about being successful in Japan and that business plan is crumbling." -- Peter Moore, 24 hours before his Microsoft resignation














botimage
Copyright 2014 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki