5 ms·
The big one for me was, when flash crashes in Chrome, only 1 tab is affected. In Firefox the whole browser crashes. And no, disabling flash and avoiding it is n
by ChrisNorstrom 14y ago
The big one for me was, when flash crashes in Chrome, only 1 tab is affected. In Firefox the whole browser crashes. And no, disabling flash and avoiding it is not an option, not with online video and music playing through flash. One day when flash is gone this won't be a problem but we haven't reached that day yet.
My usage is now 99% Chrome, 1% Firefox (for testing purposes), and keep in mind I was one of those die-hard Firefox fans. I bought my Firefox t-shirt from the Mozilla store, installed it on school computers, supported it from the beginning and everything. Now I'm all Chrome and so is my whole family.
Looking back, the 3 main reasons why I loved Firefox was that was open source, which was emotionally appealing, its call-to-action was to end the tyranny of Internet Explorer, it was standards compliant, and it had extensions. Chrome now does those very same things, some much better than Firefox, and is catching up to the amount of useful extensions. And it looks and behaves better.
I will say this, Firefox has one thing that I really love over Chrome. When you set Firefox and Chrome to remember your last tabs open and load them on each startup, Firefox doesn't load all 80 tabs immediately I open it. Instead it only loads the currently selected tab and leaves the others unloaded, thus speading things up and preventing a system slowdown. Chrome on the other hand loads all 80 tabs at once, so I have to wait 15 seconds before the browser becomes responsive again.
- azakai 14y ago> The big one for me was, when flash crashes in Chrome, only 1 tab is affected. In firefox the whole browser crashes. Firefox has run Flash in a separate process for a long time now (2 years, I think?) - so a Flash crash only brings down Flash, not the browser or even the tab for that matter (the rest of the web page will still run).
- ChrisNorstrom 14y agoHuh...I have the latest Firefox 14.0.1 and about 2 days ago I had the whole browser just slow down, crash, and self destruct because of 1 tab. I restarted it, reloaded all the tabs and it crashed again as soon as that 1 tab loaded. I think it was a news aggregator too, so it's not like it was an experimental html5 site or anything. I had to quickly kill it before it loaded on next startup. Perhaps maybe it's not flash then?
- rrmm 14y agosame for me...i'm using ff on linux, flash runs in a process called plugin-container. you can even kill it, which just kills the flash content in browser pages.
- azakai 14y agoYeah, manually killing the flash process is useful. If I see my CPU is being hogged for no reason, killing flash generally fixes it (and Firefox keeps running).
- cfinke 14y agowhen flash crashes in Chrome, only 1 tab is affected At least in Chrome for Mac, when Flash crashes, it crashes in every tab.
- cpeterso 14y agoChrome and Firefox run all instances of Flash, from all tabs, in a single plugin process. I think this demonstrates that sandboxing plugins may be less for security as for protecting the browser from Adobe's bugs. :)