Slashdot Mirror
Newest Firefox Browser Bashes Crashes (cnet.com)
Nobody likes it when a web browser bombs instead of opening up a website. Mozilla is addressing that in the newly released v53 of its Firefox browser, which it claims crashes 10 percent fewer times. CNET adds: The improvement comes through the first big debut of a part of Project Quantum, an effort launched in 2016 to beef up and speed up Firefox. To improve stability, Firefox 53 on Windows machines isolates software called a compositor that's in charge of painting elements of a website onto your screen. That isolation into a separate computing process cuts down on trouble spots that can occur when Firefox employs computers' graphics chips, Mozilla said.
The only reason I haven't dumped it completely yet is because there are some useful add-ons that aren't available for Chrome...
Don't worry, they work hard on phasing out XUL add-ons with version 57 at the end of 2017, so that they will have just as few add-on choices as chrome.
Maybe in 10 or 15 years Firefox will be production ready. So instead of crashing several times daily, it might only crash several times weekly.
Are you sure you're using the same Firefox as me? It crashes less than once a year, and that's on Debian unstable, with 33 extensions and hardly ever below 100 tabs. Firefox does have its flaws, such as dropping sound support, massive memory use and using lots of CPU even when idle, but crashiness isn't one of them.
If you experience crashes "several times daily", you'd better check your hardware. Or perhaps you're running some bogus DRM scheme.
The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
Because Vista = Server 2008. Some people still need to keep them servers alive for industrial purposes. With browser support fading, it is becoming increasingly difficult to keep these machines alive.
It doesn't. It's nothing like Chrome. I use Firefox exclusively, on several different platforms and I tend to keep the programme open for many weeks. I haven't had a crash in years.
Chrome has tons of choices for extensions... that haven't been updated in 4+ years.
So instead of crashing several times daily, it might only crash several times weekly. Not that you'd want to run it that long without restarting the app since it'll be using all of your memory by the end of the day.
Is there a different Firefox than the one I'm using? The machine I do the majority of my browsing on is a Win 7 box with 16GB of RAM. I haven't seen a crash in at least a year, probably more. I have had 15 separate windows open with 10 to 30 tabs open in each for the last 2 or 3 months. I just rebooted today for updates. I will shutdown and restore my Firefox session when the memory usage creeps up and bogs it down. But the most I've seen it get up to is a little over 8GB of RAM usage. Which is ridiculous, but not as bad as you seem to be exaggerating it to be.
My one big sticking point to switching browsers is the Tree-Style-Tabs add-on. I can't find a single other browser that does this well. Opera is the only other that comes close, but I can't stand that it has no way to hide the tabs across the top of the browser. I could live with the vertical tabs not being nested if I cold just find a way to hide the horizontal ones.
We at Moz://a are pleased to announce that Firefox 57 will be the Chromium source code with all the icons changed to the Firefox logo. Now we don't have to actually work on our browser we can make fun of extension developers and see all the hard work they done wasted while we roll in the Yahoo sponsorship money.
On 6200 Windows clients and 1900 Mac's. Firefox is above and beyond the most crash prone browser - it even tops IE 11 (Fwiw Chrome > IE 11 > Firefox are the most used browsers in my organization according to software metering).
I use Firefox as my main browser, and I understand the problems some people have with it. Thing is, I tend to see Firefox's flaws as emerging from using it with lots of addons as intended. Adblock + noscript + various EFF tools are bound to bork it from time to time. I'm kind of impressed it's as stable as it is. Not to mention I'm the kind of crazy person who has 300 tabs open right now.
I used to use Opera as my secondary, back before they dropped Presto and abandoned their very functional email/rss components. Now it's Chrome with adblock.
It might be ironic that my favorite mobile browser was Safari with adblock. Never had a single problem with it. Plus Apple for all their faults has been willing to tell bloatware peddlers to go hang themselves.
Marketing genius! Is it tough on crashes? Does it stamp the crashes out? Does it get the crashes before they get you? I could keep doing this all day. If you'd like I can hire my marketing skills out on a very affordable rate.
We'll make great pets
In "about:config" change "fayout.frame_rate" from -1 to 60 (or whatever your monitor runs at). For some stupid reason, Firefox renders as fast as your CPU can handle 100% of the time. Even at 60 FPS, it uses ~1% CPU when idle so I'm guessing it was going like 6000FPS when unrestrained.
Mind the frickin' laser...
system load just dropped by 0.8
Why the fuck is this not the default?
dafuq, mozilla...
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion. -- Spazmania (174582)
Yes, Tell that to us. Just a couple weeks ago I had to search in more than 50 computer shops and stores and fail to find a computer capable of running DOS and latest version of general-electric PLC programming software that they still claim support for. because no one in here has anything older than 3 intel tics.
Yes, Please do blame us 3rd world countries for holding you back.
Am from Iran, 3rd world and all the import/export drama.
Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion. -- Spazmania (174582)
I've found that some (most?) Linux distro's recompile FF to their release packages, instead of simply using the Mozilla provided binaries.
This creates a much more stable browser.
I use Funtoo Linux, and always go the compile route when updating FF. The one time I decided waiting for it to compile would be too long (was in a time crunch) it was a terrible experience. When I later "upgraded" to the self-compiled version it stablized.
I guess a lot of it depends on what your system has for native libs, and compatible versions. If you're using a huge binary blob from Mozilla you're missing out on utilizing shared libraries, and possibly using out-dated, bundled in versions of those libraries.
The browser should render by default at vsync with the -1 setting. Perhaps the detection fails on some platforms?
that is why they want to drop the old add-on support and use a model mostly compatible with chrome.
Current add-ons are too close to the firefox code and they can not mess with the code without breaking add-on or creating never-ending compatibility layers.
With the new add-ons api, this will get more stable and easier to port add-ons back and forward from/to chrome
Higuita