Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
What's the point in that? A browser is not exactly a processor intensive app, 1 core is really enough.Ditched firefox since I found out it wasnt multi-threaded.
I'm pretty sure chrome is multi threaded?
What's the point in that? A browser is not exactly a processor intensive app, 1 core is really enough.
If firefox was multithreaded, the only advantage that would give, is when it crashes, all cores-->100%utilization=unresponsive system, FTL.
You're probably a light user.
I facebook, flash games, while I'm tf2ing and alot of other crap.
When on firefox, my facebook and flash games slow down, found out it wasn't multi-threaded, switched to chrome, no slow down.
Problem Solved.
The reason is facebook is very javascript intensive, which has always been a Firefox weakness (until 3.5) and was Chrome's main strength (again, until Firefox 3.5).
I'd try 3.5 and then compare them. The new JS engine is much better than the one in 3, which should speed your stuff up.
And, as someone who routinely has over a dozen tabs open, including FB, it being single-threaded is completely irrelevant. Multi-threaded but inefficient at each one, is still inefficient.
Firefox is a major hog on most systems I use despite OS and plugin/addon variations. Updated versions haven't done much to reduce it. Inevitably it'll bloat upwards of 500-700MB despite closing down tabs. Memory cache releasing plugin doesn't work. The annoying thing is that I could run it for a week, have it bloat, make one new tab with no history, close all the other tabs, clear the caches and it'll still be eating up 500-700MB on a single blank page. So I just go through the habit of saving my tabs, restarting FF every so often to keep it from chomping more memory than it should. Though I did have a fun incident about this time last year. FF leaked and took up 1.5GB physical memory, 1.7GB virtual. Couldn't even end task on it (was still running WinXP full time then) or use process killer to nuke it. On a system with 2GB installed, yeah. Brought my system down to its knees to where I had to power off reboot. Despite Linux, FF still has the same memory management issues.
I've used Chrome and have it installed on other systems, mine and roommates. Certain sites like Break.com, select Youtube embeds, ComedyCentral videos... the videos won't start in FF, probably due to the hosts file and adblock combination I use. I load the URL in chrome and the videos start up just fine.
On my netbook with the slow SSD (Aspire One, 8GB SSD with average writes of about 0.5MB/sec) inside of it... I use Opera 9.5 with disk cache disabled. Loads quickest and Hulu lags the least with it. Good enough for watching the occasional Conan episode or drama/comedy film before I turn in.
FF was good. When it was still called Phoenix. Now it's a hog and really needs to "go back to the basics", what Phoenix was created for in the first place.
As far as Chrome goes, someone complaining that FF uses less ram total compared with Chrome... that's because Chrome runs each tab as a separate process. Each lump of memory that is used actually gets freed when you close things off whereas you'll end up with a larger allocated heap that FF is still holding up despite having tabs closed.
Once some equivalent plugins start showing up for Chrome/Chromium, I could see myself dumping FF. Not yet at this point, though.
Ok guys, lets stop this Chrome vs Firefox thing, remember, its IE who's the enemy.![]()
I seriously don't understand where people get this whole "Firefox is a hog" thing. Maybe the whole memory leak thing happened in the past, but I haven't seen anything of the sort since mid-Firefox 2 era. Check my post with the screenshots - Firefox, with 3 tabs open and all of my extensions running, uses nearly the same amount of memory (slightly less) than Chrome does with those same 3 tabs open. It apparently doesn't matter weather it's because Chrome runs in separate processes or not - because memory usage is pretty much the same, with Firefox having a slight upper hand. It also appears that Firefox is lighter on the CPU, as well. Well, that's obvious, since it's only 1 process as opposed to numerous processes depending on open tabs for Chrome..
I think its safe to say...
once you go chrome, you wont go back
how many people have honestly given chrome a shot and went back to FF or IE ?
I think its safe to say...
once you go chrome, you wont go back
how many people have honestly given chrome a shot and went back to FF or IE ?
how many people have honestly given chrome a shot and went back to FF or IE ?
Firefox is a major hog on most systems I use despite OS and plugin/addon variations. Updated versions haven't done much to reduce it. Inevitably it'll bloat upwards of 500-700MB despite closing down tabs. Memory cache releasing plugin doesn't work. The annoying thing is that I could run it for a week, have it bloat, make one new tab with no history, close all the other tabs, clear the caches and it'll still be eating up 500-700MB on a single blank page. So I just go through the habit of saving my tabs, restarting FF every so often to keep it from chomping more memory than it should. Though I did have a fun incident about this time last year. FF leaked and took up 1.5GB physical memory, 1.7GB virtual. Couldn't even end task on it (was still running WinXP full time then) or use process killer to nuke it. On a system with 2GB installed, yeah. Brought my system down to its knees to where I had to power off reboot. Despite Linux, FF still has the same memory management issues.
I've used Chrome and have it installed on other systems, mine and roommates. Certain sites like Break.com, select Youtube embeds, ComedyCentral videos... the videos won't start in FF, probably due to the hosts file and adblock combination I use. I load the URL in chrome and the videos start up just fine.
On my netbook with the slow SSD (Aspire One, 8GB SSD with average writes of about 0.5MB/sec) inside of it... I use Opera 9.5 with disk cache disabled. Loads quickest and Hulu lags the least with it. Good enough for watching the occasional Conan episode or drama/comedy film before I turn in.
FF was good. When it was still called Phoenix. Now it's a hog and really needs to "go back to the basics", what Phoenix was created for in the first place.
As far as Chrome goes, someone complaining that FF uses less ram total compared with Chrome... that's because Chrome runs each tab as a separate process. Each lump of memory that is used actually gets freed when you close things off whereas you'll end up with a larger allocated heap that FF is still holding up despite having tabs closed.
Once some equivalent plugins start showing up for Chrome/Chromium, I could see myself dumping FF. Not yet at this point, though.
FYI, Firefox uses the least amount of RAM of the major browsers (incidentally Chrome uses the most). This is with the 3.5 RC, but it should make it clear that your problem doesn't occur with a vanilla install. Maybe you have a rogue extension or some such eating up your RAM, but it isn't Firefox that is doing it: http://www.favbrowser.com/browser-m...-safari-4-opera-10-beta-google-chrome-30-dev/
*sigh*
Read my fucking posts before you respond to them.
I can use Firefox. Use it for a week straight so it gobbles up memory. Shut down all tabs but one, a blank tab with no history... and it will still consume 500MB of ram.
Well, how many of us do you suspect keeps a browser open for a week straight? Even if I did - what is 500mb, anyways? That's pocket change on any modern system. I mean, that's not to say I want a simple web browser using that much RAM on an average basis, but the fact is - it doesn't. It only uses 40-60mb at a time, rarely (if ever) ever getting up in the 80-100mb margin.
On load, a virgin Firefox install eats 60-80MB on most systems.
It CAN be a problem when you're installing it for people with low incomes and the best system they have is still under the 512MB mark.
It CAN be a problem when you're installing it for people with low incomes and the best system they have is still under the 512MB mark.
My kids have computers I've built from parts I got for free. Those systems have XP, and 384 or 512MB. They can run firefox with a handful of tabs, an IM, and one or two other apps without pagefile thrashing. It's not a problem, if you have trimmed away all the automatic, self-starting taskbar programs.
Am I the only one who finds it ironic, that google toolbar is not available for google's browser?
![]()
for the same reasons as any other browser.Why would Google's browser need Google's toolbar?
for the same reasons as any other browser.
If the same functionality of google toolbar can be achieved with chrome, I have not found it yet.
*sigh*
Read my fucking posts before you respond to them.
I can use Firefox. Use it for a week straight so it gobbles up memory. Shut down all tabs but one, a blank tab with no history... and it will still consume 500MB of ram.
I can use Chrome. Use it for a week straight. Because every tab is a separate process, all of the memory each tab was using is released by the program. If I load up all the same tabs I had open in Firefox in Chrome... sure, it may use up more memory. But as I close down tabs that I no longer need open, Chrome's total memory usage will shrink. Firefox's WON'T.
I've duplicated this specific issue on vanilla installs. FF's memory management just sucks.
--- Final memory used ---
Figures taken after all tabs were closed at end.
Chrome: 109.49 MB
Firefox: 106.66 MB [Smallest]
Opera: 441.49 MB [Largest]
Safari: 349.62 MB
Firefox 3.5 has no problem freeing used memory. In fact, it is the *best* at it. Firefox 3.5 has the *best* memory management across the board. I have no idea what problem you are having, but it clearly doesn't happen with a vanilla Firefox 3.5 install on a clean system. I have the same results as the article's all the time. I leave Firefox 3.5 running for weeks at a time as well - it never hogs memory.
I'll go ahead and stay in Windows when I load up later tonight to go play L4D. I'll stay in it for a week and post my findings. I will be using a vanilla Firefox 3.5 installed to a different directory with no extensions. The most I will do is configure the appearance to my standard layout. I will also disable disk and memory cache to avoid skewing the results due to history.
Doubt anyone will see this in a week, but I'll have this thread bookmarked so I can show you how it look on my end. If there's one thing that I have learned about Firefox, its memory bloat and failure to free up resources is consistent across many different installs and configurations.
Why Windows? Because Firefox for Linux -sucks.- I find running the Win32 version of Firefox in Wine to be a lot more stable and responsive. This probably would be a bad metric to go by as it's Wine on top of Firefox and definitely not a standard user's setup.
Again - you're going to be running the program in a very unrealistic nature. No one uses their browser for a week straight without closing it. I'm sure that ANY program being run for a week straight will start to cause issues of slowdown due to memory management. So, in essence - it will be your unrealistic findings vs. all of the findings and testing we've shown you that PROVES that Firefox is one of the lightest browsers available - even WITH many extensions and add-ons running.
So, have fun.![]()
I leave Firefox running until Windows makes me restart. So do a lot of my coworkers. The unrealistic part is that he will be modifying options, options that could vary well have a major impact on exactly what he is testing.
I leave Firefox running until Windows makes me restart. So do a lot of my coworkers. The unrealistic part is that he will be modifying options, options that could vary well have a major impact on exactly what he is testing.
Indeed. Still, though - after weeks, any program will start to give problems. Most of the time it's as simple as quitting the program and restarting it.
ANY program?
So you're telling me they reboot servers and restart IIS and Apache daily, that 200+ day uptimes are just a fluke? I mean, I don't mean to split hairs here, but you could be a little less broad in your statement. An OS, by definition, is a program as well.