"Firefox may hang if left open for long periods of time. To fix the issue, restart Firefox." Oh my God...
This is more-or-less exactly what you do with Chrome all the time. Because each tab is a separate process, you're implictly closing and opening it for each new tab.
Firefox is slow - troubleshooting
11–20 of 25 posts
Re: Firefox is slow - troubleshooting
#12Earlier quoted context omitted.
This is more-or-less exactly what you do with Chrome all the time. Because each tab is a separate process, you're implictly closing and opening it for each new tab.
I pointed this out on a Reddit thread quite a while back, started by some Firefox devs. Or maybe it was Opera devs. Anyway, I was surprised by the response: neither the devs, nor other commenters in the thread, saw the benefit to making every tab its own process.
Furthermore, firefox 4 does have some separate processes (not per tab). Note that chrome's default is not per-tab either.
Re: Firefox is slow - troubleshooting
#13Re: Firefox is slow - troubleshooting
#14Earlier quoted context omitted.
I regularly ran Firefox 3.6 (I'm on v4 now) for weeks at a time, and never had such issues. I'd guess it's an extension or plugin you had installed. My biggest problem with Firefox (v4 only) is shutting it down takes ages as it iterates through every file in the cache, which is encrypted on my machine. I limited my cache size to 50MB, which seems to have limited the pause times to something reasonable. I cannot stand…
I do have a few extensions installed & enabled -- AdBlock Plus, Firebug, Greasemonkey (rarely used, I should just uninstall it), Flashblock, and YSlow. But, I've seen similar behavior on at least one other system, and the only extension we had in common there was AdBlock Plus. The behavior also predates Greasemonkey. The other system is newer, and the slowdown there is less pronounced (though still noticeable), which…
Re: Firefox is slow - troubleshooting
#15"Firefox may hang if left open for long periods of time. To fix the issue, restart Firefox." Oh my God...
To prevent this from happening don't use flash with Firefox or really any browser! It can handle one or two instances of flash running at the same time but anymore watch out .. FlashCrash!
Re: Firefox is slow - troubleshooting
#16Earlier quoted context omitted.
There's also an "AddBlock Plus" for Chrome, and a short test shows it that works decently, but I don't know if the quality is the same. Maybe worth a try?
Chrome's ad blocker grabs items after they've downloaded and (briefly) displayed on the page, and then hides them. Also, Chrome is still not available for my aging PPC.
Re: Firefox is slow - troubleshooting
#17Earlier quoted context omitted.
There's also an "AddBlock Plus" for Chrome, and a short test shows it that works decently, but I don't know if the quality is the same. Maybe worth a try?
Chrome's ad blocker grabs items after they've downloaded and (briefly) displayed on the page, and then hides them. Also, Chrome is still not available for my aging PPC.
Re: Firefox is slow - troubleshooting
#18Earlier quoted context omitted.
I pointed this out on a Reddit thread quite a while back, started by some Firefox devs. Or maybe it was Opera devs. Anyway, I was surprised by the response: neither the devs, nor other commenters in the thread, saw the benefit to making every tab its own process.
IPC is very expensive. Furthermore, firefox 4 does have some separate processes (not per tab). Note that chrome's default is not per-tab either.
I have trouble taking that at face-value; Linux seems to do OK with it and, for a while, there was a little-bitty web browser for Macs called Stainless (http://stainlessapp.com/) that did one-process-per-tab, and it seemed quite performant. Better, in fact, than all other browsers at the time. Unfortunately, it hasn't been updated in about a year now...
> Note that chrome's default is not per-tab either.
Oh yeah, somebody pointed that out to me back on that Reddit thread, too. I forgot. Still, I really think it should be, and that it should be considered standard practice for all browsers.
A while back, my frustrations with browsers resulted in a quickie project that I called "Crash My Browser" (still up at http://crashmybrowser.com/). I haven't tested it with recent browsers, but, once upon a time, at least one of the tests on that page could completely cripple not just that page's tab, but the entire browser, for most browsers. Since nobody seemed to get why that was a really stupid design flaw, I figured a demonstration was in order.
Re: Firefox is slow - troubleshooting
#19Earlier quoted context omitted.
This is more-or-less exactly what you do with Chrome all the time. Because each tab is a separate process, you're implictly closing and opening it for each new tab.
I pointed this out on a Reddit thread quite a while back, started by some Firefox devs. Or maybe it was Opera devs. Anyway, I was surprised by the response: neither the devs, nor other commenters in the thread, saw the benefit to making every tab its own process.
https://wiki.mozilla.org/Electrolysis
If that page is to be trusted, Firefox on Android already does it.
Re: Firefox is slow - troubleshooting
#20Earlier quoted context omitted.
This is more-or-less exactly what you do with Chrome all the time. Because each tab is a separate process, you're implictly closing and opening it for each new tab.
I pointed this out on a Reddit thread quite a while back, started by some Firefox devs. Or maybe it was Opera devs. Anyway, I was surprised by the response: neither the devs, nor other commenters in the thread, saw the benefit to making every tab its own process.