Multi-Process Comes To Firefox Nightly, 64-bit Firefox For Windows 'Soon'
An anonymous reader writes with word that the Mozilla project has made two announcements that should make hardcore Firefox users very happy. The first is that multi-process support is landing in Firefox Nightly, and the second is that 64-bit Firefox is finally coming to Windows. The features are a big deal on their own, but together they show Mozilla's commitment to the desktop version of Firefox as they both improve performance and security. The news is part of a slew of unveilings from the company on the browser's 10th anniversary — including new Firefox features and the debut of Firefox Developer Edition.
Oh wait.
As a long time Firefox user who switched to Chromium, I am happy to see that Mozilla is taking these steps to ensure long term survival. Multi-process architecture is long overdue. I still maintain that Firefox has one of the most friendly developer communities out there.
Somewhere, something incredible is waiting to be known. -Carl Sagan
Agreed. Nothing else comes close imo.
Somewhere, something incredible is waiting to be known. -Carl Sagan
YAY!
It only took them three years exactly.
it would be exactly like Chrome :)
Waterfox 64 bit seems to work fine, have been using it for a while now as Firefox memory limits were just too annoying.
I'm hoping for a return to the Netscape Navigator v3 interface, myself.
Yes, it is too bad that developers often want to do new shiny things instead of usable things.
Multi-process is the major reason I use Chrome. One tab freezing up the entire app, or even just making other tabs slower, is unacceptable.
Then this hits general availability I'll definitely be re-evaluating Firefox.
The multiprocess option was introduced a while ago. I tried it for about an hour, but any time I had more than about 5 threads open, it would hang the computer, and I couldn't do anything. This could be because I was on a relatively underpowered laptop, but... I am just going to stay away from it till it's more mature. It's honestly the only thing in Nightly that has made me look for a way to turn it off.
We prefer Firefox, but I was about to switch my wife over to using Chrome as it has become impossible to figure out which of the dozens of tabs she has open was slowing everything down, even with ad-blocking enabled. It will be interesting to see how the multi-process support impacts memory overhead, though, as Firefox has had the lead on Chrome in that area.
Use Sea Monkey - Netscape Communicator theme and related extras supported forever without change.
http://www.seamonkey-project.o...
Democracy Now! - uncensored, anti-establishment news
But is it still crash-happy, memory hogging, processor intensive, crap?
...plus "e10" still doesn't play well with copy/paste nor gmail compose window editing. ah well, i admire their dogged efforts.
you can give palemoon a try
When Firefox 30 came out, I decided go with the flow (previously I tried keep interface same, with menubar and status bar). After a while I got used to the new interface. I don't miss my old interface.
Its a great feeling to see the programming conventional wisdom of the last 20 years get reversed!
So many have been preaching of the blocking I/O + thread style I've always felt like a radical.
Now, with the rise of non-blocking and child processes, the worm has turned !
Get thee hither LWP's, mutecies, and deadly embraces.
Pale Moon has been available in x64 for a long time now, and doesn't have advertisements bundled into it.
I'll just stay put.
I've been using Firefox for the past six months or so because I don't like Chrome, but Chrome still has the technology edge in several cases. This looks to be bridging at least some of that gap. It would have been better if it happened three years ago, but late is better than never.
If you can't convince them, convict them.
That is the tell-tale mark of a new (meaning inexperienced) programmer.
I can't remember the last time FF gained a new feature I actually gave a fuck about. I've gotten completely accustomed to FF updates only removing/neutering useful features and covering the GUI in Play Dough. Multi-process support would be a genuinely meaningful upgrade for once, but I agree there's no way it would make up for Australis.
The new interface doesn't work for my work flow, but with that said OP is being overly dramatic. The classic theme restorer with a couple other extensions does restore the interface to how it was previously. Some ppl just have the need to complain even though there are solutions out there.
Multi-process is probably the most important feature of modern-day browsers, especially with modern html5 sites and web-apps.
It's a pretty big disgrace that this wasn't implemented before, and that Mozilla instead concentrated on a mobile version and Firefox OS.
And I think it's because of this single feature, that made firefox so sluggish and eventually crash and die after consuming over 2gigs of ram, and the reason why so many people moved away to a more responsive browser like Chrome (which was multi-process from day 1).
I'd add two things onto that:
1: The ability to click-to-play for add-ons. Chrome has this, and it does a great job at dealing with the loud ads that autoplay. This also adds security so that malware from a compromised or dodgy ad server doesn't get free reign to execute.
2: A VM-like structure similar to Chrome, so that a compromised window or tab is limited to just that context and can't take down the whole browser, or even worse, the user context it runs in. Chrome's VM is a big security plus. Not 100% security, but quite useful.
The article is about the addition of 2 to Firefox Nightly. For 1, I have been using Flashblock for years. It's so effective at controlling bullcrap ads that I really haven't needed any other ad blocker, even on an old 10" laptop with an Atom CPU and 1 GB of RAM.
I switched to Chrome a while back when it came out. It supported most of the then new HTML5 features, most importantly, playing youtube videos without flash. At first I used chrome sparingly, it took a bit to get used to. Then, after a few vulnerabilities were found in FF which could allow attackers to read the memory of other tabs, I switched. The internet is a dangerous place, multiprocess sandboxing of tabs made perfect sense. I also really liked its UI which was much more simple: tabs, URL bar and a few controls like forward, back and reload along with a settings button.
But it came with a cost. I connected it to my google account and it also integrated with my phone and tablet bringing my bookmarks, passwords and other credentials across all of my devices. So I am hooked on the convenience of Google integration, for better or worse. Worse most likely. Plus logging into sites that use Google is very convenient. I'm addicted.
So going back to FF for me will be difficult.
My only concern with multi process is memory footprint. FF is great for low memory systems like virtual machines and older systems. Chrome is a memory hog and easily uses a gigabyte or more. Right now with 8 tabs open I have 12 chrome processes, two are close to consuming nearly 300 megs each, one nearly 200 and the remaining are anywhere from 12-87 megs. I assume the three large processes are the ones running the show (windows, IPC, etc). The largest being the parent process that spawns the others. The smaller 8 processes are the actual tabs. That is pretty much 1 gig of RAM for 8 tabs. I have computers and VM's with less running various test systems. FF on those machines clocks in at 250-300 megs under heavy use.
My daily web browser is Nightly. A few days ago when they enabled e10s by default I found out about the change because my browser crashed on startup. The only way I could get it working again was to start Nightly in Safe Mode and disable e10s. Multiprocess in Nightly is varying states of very broken for most addons. For me the key ones are HTTPSEverywhere, Adblock Plus, and Reddit Enhancement Suite. None of these addons are functional with e10s enabled currently.
Catching up to Chrome 1.0 ... eventually! :)
Notice they add the new advertising features yesterday and then make the things people want (official 64-bit support, better performance) a future version feature.
Gotta take your medicine before you get candy.
Firefox has had the ask-to-activate for flash for some time. Go to about:addons, select plugins from the menu on the left, and next to each plugins there is a menu where you can select ask to activate.
Its like when I gave the 32 bit version of Visual Studio to a colleague and he complained that he wanted the 64 bit version.... there is no 64 bit version because it isn't needed.
A lot of developers want to make use of runtime speed benefits of whole-program optimization, which can perform inlining, nonstandard fast method call conventions, and other optimizations despite the caller and callee being in separate source code files. And with a program as big as Firefox, this has taken more than 4 GB for three years. Or is Visual Studio just a 32-bit GUI for a 64-bit compiler that does the actual compilation and linking of such large programs?
Tools -> Add-ons -> Plugins -> find plugin of choice, change it from "Always activate" to "Ask to activate"
That's on Linux, anyway. Add-ons menu might be somewhere else on your platform, but you should otherwise be able to do what I do.
64bit... again, bragging points about how many bits you use, no functional difference to anyone.
Unless of course you want to address more than 4GB of memory.
Flashblock doesn't help with the "update java" ads, which is a line of Javascript from a compromized ad network that brings you to a page that tries to auto-download something.
You have to go one-step further with NoScript, and whitelist the sites you visit most frequently.
Well, I currently have 11 windows open with a total of about 230 tabs, Firefox was fine until it went over 3 gigs and then it just stopped, with every action taking 30+ seconds to do.
Umm, why in $diety's name do you need 230 tabs open? You cannot possibly use that many efficiently. It's a scientific fact that you cannot multitask worth anything (no one can). Hell you cannot even find a particular tab efficiently with that many open. That's one of the most baffling work "flows" I've ever heard of. Just because a few tabs are good doesn't mean a huge number is better.
Reloading a bookmark requires that your laptop have a connection to the Internet. Loading pages in tabs allows reading them while offline. The city bus system in Fort Wayne, Indiana, for example, does not offer Wi-Fi to paying riders. Nor will airlines now that AT&T has given up on in-flight Internet. Tabs mean you don't have to spend $400 a year on cellular Internet for your laptop.
Or one who doesn't have to release saleable products to pay their wages.
Firefox is dog slow in Ubuntu box (Core I5!) always taking 20%-30% cpu.
Chrome, not much better. Just tried Opera Developer (chromium based I believe) and the difference is abysmal. 0% cpu at idle, fast as lightning, I installed lots of plugins into Opera and it still it consumes no CPU. Why Firefox or chrome can't be like this?
All very nice to hear about shiny new features, but I would be even happier to hear Mozilla foundatation announce that they plan to fix the longstanding bug where 200 open tabs causes firefox to crash every two days or so.
Oh, also announce that the bug where keystrokes go to the wrong window will be fixed. Thxbai.
When all you have is a hammer, every problem starts to look like a thumb.
...is for them to stop fucking with the interface. If I wanted tabs, I'd use chrome; stop trying to shove them down our throats.
That would be a big step up from Australis. At least that UI followed proven UI conventions like menu bars, tool bars, and status bars. It was easy to usr, unlike Australis.
Many file transfers don't start at all, and the Ctrl+s or save page doesn't work yet, to add some more.
Maintenance programming is boring, tedious and hard. Testing anything is mind-bogglingly ridiculously difficult because most places don't have good configuration management. Given the challenge and the risks involved most programmers prefer the shiny new thing which has no test requirements and no operational risk.
I don't use the new interface either, but still I can arrange myself without addons. When I need to access one of the menus, I simply press alt, and get the old menu bar. I only hope that they won't remove this in future.
Yeah, you're right. Why should users complain just because they've made the standard interface unusuable, so you have to install random extensions to use their product?
1: I use Flashblock for that. There's probably some equivalent for Java, but I don't even have the Java plugin installed.
factor 966971: 966971
I just started using CyberFox browser. I suppose I 'll switch to FireFox again for consistency with Android and Windows XP systems.
The so-called paradox of freedom is the argument that freedom in the sense of absence of any constraining control must lead to very great restraint, since it makes the bully free to enslave the meek. The idea is, in a slightly different form, and with very different tendency, clearly expressed in Plato.
Less well known is the paradox of tolerance: Unlimited tolerance must lead to the disappearance of tolerance. If we extend unlimited tolerance even to those who are intolerant, if we are not prepared to defend a tolerant society against the onslaught of the intolerant, then the tolerant will be destroyed, and tolerance with them. — In this formulation, I do not imply, for instance, that we should always suppress the utterance of intolerant philosophies; as long as we can counter them by rational argument and keep them in check by public opinion, suppression would certainly be unwise. But we should claim the right to suppress them if necessary even by force; for it may easily turn out that they are not prepared to meet us on the level of rational argument, but begin by denouncing all argument; they may forbid their followers to listen to rational argument, because it is deceptive, and teach them to answer arguments by the use of their fists or pistols. We should therefore claim, in the name of tolerance, the right not to tolerate the intolerant. We should claim that any movement preaching intolerance places itself outside the law, and we should consider incitement to intolerance and persecution as criminal, in the same way as we should consider incitement to murder, or to kidnapping, or to the revival of the slave trade, as criminal.
Karl Popper, Vol. 1, Notes to the Chapters: Ch. 7, Note 4
Paradox is not necessarily a fallacy, and blind moral relativism is not a good thing. There is no need to be tolerant of the views of murderous dictators, rabid extremists, or any other group which opposes freedom and tolerance. Resisting bigots results in more tolerance, not less (although if you're a bigot you might think the distribution is unfair).
Those who advocate genocide deserve every protection afforded by law, and none afforded by common human decency.
That's true, on Ubuntu Unity pressing Alt gets me the context menu in the dash, which is awesome!! oh... I'll get my coat.
now firefox can use more then 4 gigabytes of ram !!!
- internal GC is a big issue
- 32bit and 2-4 days of use: not good
- finally not EVERYTHING is dying or blocking when some tab rendering runs amok
It's like the best browser ever: .. said no-one ... well, at some time after 1.0.7 and the present I guess.. considering that's 30+ versions I don't really know where.
http://i61.tinypic.com/2yvs96o...
http://i61.tinypic.com/33c5g07...
Untrustworthy piece of shit browser.
Of course Chrome have crashed a few times too (ran out of filedescriptors in Linux?)
Firefox just became slower and slower, I closed tabs and have open other ones and it have behaved badly and changed around windows very now and then (happened at lots of sessions too) but currently it seem stone dead.
64bit? Welcome to the 1970s.
Or you might right-click anywhere outside of the tabs and URL bar, and click on "Menu bar", then the menu is shown permanently. No add-on, no options editing and you get a Windows 2.0 compliant / Motif compliant application already.
Just complaining a bit isn't a problem. It's when you don't stop, and instead just get louder. The best is when people complain for Firefox to hurry up and give them a modern browser capable of beating Chrome, yet they complain that Firefox has to break some things along the way to get there.
You mean this NetscapeNavigator? Looks like it also uses those big touchscreen tablet/phone buttons which take up 1/3 of the window that everyone hates so passionately. Maybe your memory's a little foggy.
every release broke it more and more. for several years.
Mod parent up! It's something many people would like to read.
Pale Moon x64 is Firefox with adult supervision.
Firefox is becoming less and less stable. It's so unstable that it often doesn't report crashes, so the crash reports aren't reliable, they show far fewer crashes than actually occurred.
The underlying problem is that Mozilla Foundation needs better management. At present, Mozilla Foundation management is sometimes excellent and sometimes very unreliable.
But will it support a 64-bit JRE on Windows?
"Love heals scars love left." -- Henry Rollins
"... couple other extensions..."
What other extensions restore Firefox to the previous usability? Most people don't have the time to search.
Ive been running Waterfox (64 bit firefox) for several years now. I'm not sure what difference it really makes but makes me feel better.
Because it's not actually "unusable" by any stretch of the imagination, and it is just ridiculous whining to claim it is?
If 36.0a1 is any indication of what to expect in the future, we should all just switch to IE and burn in hell. It'll be a better experience and it won't hurt as much.
Have loved and used Firefox for years, but last several versions (past v28) have crashed frequently for me (Win7) with what appear to be memory leaks and then the ironic submitted crash report. I'll be looking forward to multi-threaded 64-bit crashes and memory leaks!
A move to multi-process in Firefox can be bad news for anyone using multiuser thin client environments (uncommon but still used). On a shared system, you generally want to have control over which applications can use multiple processes, lest they can go runaway and eat up all cores and resources on a system. Traditional tools such as "nice" don't scale well with single applications that can throw off dozens of threads. As an example- JAVA is *extremely* hostile in a a thin client environment (not just CPU, but RAM too). Just one person starting it can "pause" a 24 core Xeon server for dozens or hundreds of users due to improper assumptions about resource availability.
So I really do hope that Mozilla makes the number of processes allowed ADJUSTABLE in the settings....