In Mozilla's defense, they've handled Places-related issues well in the past.
http://shaver.off.net/diary/2008/05/25/fsyncers-and-curvebal...
Dear Mozilla: Fix Your Damn Browser
31–40 of 211 posts
Re: Dear Mozilla: Fix Your Damn Browser
#32I dropped FF b/c of the memory leak. As a test, on a spare mac I wrote a script that launched FF and Chrome simultaneously and visited 10 websites I frequent. They both had similar clean profiles. After roughly two days of continuous refresh/load cycles, Chrome's memory was at 148MB, FF was 988MB.
What version of Firefox? As of 7, memory usage is almost as good as Opera for me.
Re: Dear Mozilla: Fix Your Damn Browser
#33I remember one of my co-workers telling me that Firefox was running great for him now that he'd upgraded from 4GB of RAM to 8GB. It finally wasn't slowly grinding to a halt any time he had more than a handful of tabs open for more than an hour or two. Seemed a bit like Stockholm Syndrome to me.
How long ago was this? There's been a number of memory usage improvements since 3.5.
I had 40 tabs open for the better part of last week and didn't notice a performance hit; and I've only got 2Gb RAM.
Re: Dear Mozilla: Fix Your Damn Browser
#34At least with Firefox you don't have to deal with things like this: http://code.google.com/p/chromium/issues/detail?id=41467 When Firefox dropped http:// at least they gave you the ability to turn it back on!
Who cares? The only use case people were complaining about was copy/paste not inserting the http://, which it does now. What, exactly, is the issue, and why are people still whining about it?
Re: Dear Mozilla: Fix Your Damn Browser
#35I remember one of my co-workers telling me that Firefox was running great for him now that he'd upgraded from 4GB of RAM to 8GB. It finally wasn't slowly grinding to a halt any time he had more than a handful of tabs open for more than an hour or two. Seemed a bit like Stockholm Syndrome to me.
How long ago was this? There's been a number of memory usage improvements since 3.5. I had 40 tabs open for the better part of last week and didn't notice a performance hit; and I've only got 2Gb RAM.
I have the latest version and my long running high count tab sessions slow down my system tremendously. OSX 8GB RAM.
Re: Dear Mozilla: Fix Your Damn Browser
#36As a dev, FF was my go-to utility browser due to Firebug. Google released Chrome, and I found myself using FF rarely. I rebuilt a laptop recently. After loading it up with software, it was a good 3 weeks before I even noticed that I didn't have FF installed.
I've had a similar experience. I've really come to appreciate Chrome's built in developer tools and have pretty much left Firebug in the dust.
I'm in the opposite boat. I find firebug easier to use for the limited use cases I encounter (mostly scraping html id tags) than Chrome's dev tools.
That said, I still far prefer Chrome as a browser.
Re: Dear Mozilla: Fix Your Damn Browser
#37I share the same feeling. It is becoming a pain. If I keep it open for few hours, it inevitably crashes and needs a restart. I started using firefox few years back only because it won't crash and is stable. Not anymore I guess!
Re: Dear Mozilla: Fix Your Damn Browser
#38> Firefox, on Linux at least, is busted. It’s busted so bad that it’s painful to use. And it’s been this way ever since Firefox 3 launched — three years ago.
This is an odd statement, considering that many Firefox devs run Linux. I'm running Firefox on Linux right now, and it works great.
I guess the author of the article is hitting a specific bug. It isn't a general issue that affects all users of Firefox on Linux.
Re: Dear Mozilla: Fix Your Damn Browser
#39At least with Firefox you don't have to deal with things like this: http://code.google.com/p/chromium/issues/detail?id=41467 When Firefox dropped http:// at least they gave you the ability to turn it back on!
I'm impressed by the passion with which people want http:// back in their URLs. Perhaps it's tangential to the original thread, but why's it such a big deal?
It gets in my way doing copy-paste. I don't entirely understand it - it seems to have something to do with whether Firefox is busy or not - but it's easy for a copied URL to simply not have the prefix, which breaks subsequent use pretty frequently (eg. 'google.com' is not a useful Markdown link while 'http://google.com is).
Re: Dear Mozilla: Fix Your Damn Browser
#40I remember one of my co-workers telling me that Firefox was running great for him now that he'd upgraded from 4GB of RAM to 8GB. It finally wasn't slowly grinding to a halt any time he had more than a handful of tabs open for more than an hour or two. Seemed a bit like Stockholm Syndrome to me.
I've got an Asus EEEpc with 2GB of RAM and 4GB swap and I always have Firefox open with 80+ tabs in 4+ windows. After a week or so it'll get really slow when loading and would crash in a day or two if usage continued, so I just kill it and it reloads everything.
This "more than a few tabs" or "more than an hour or two" is craziness? What is your friend running?