Quote:
Originally Posted by zelda_pinwheel
i also launch my browser first and then leave it open ; but i've noticed that firefox tends to use more and more memory when i do that, which chrome doesn't (usually) seem to do as much (and i'm sure you're right, it's probably an extension causing trouble. the trouble is, the whole point of using firefox, in my eyes, is for the extensions, so i don't really want to give them up...).
|
FF had memory leak problems in 3.0.X, that seem to have been stomped in 3.5.
I
did just uninstall the Brief RSS reader extension in my Ubintu install, after watching memory use steadily climb when the browser was idle and not being used. It looks like Brief's periodic checks for feed updates cause memory leaks. The problem is, I can't find a good RSS reader for FF. I was happily using Sage, but that's apparently been abandoned by the developers and has compatibility issues with FF 3.5/6. Brief was close in behavior, but leaks. Nothing else available works as I prefer.
The current lineup of extensions under Windows is:
Enabled Extensions: [13]
-
All-in-One Sidebar 0.7.11
-
Brief 1.2.5
-
CuteMenus - Crystal SVG 1.9.3
-
Ghostery 2.0.2
-
Gmail Notifier 0.6.4.1
-
Greasemonkey 0.8.20091209.4
-
Image Zoom 0.4.2
-
MR Tech Toolkit 6.0.4
-
NoScript 1.9.9.42
-
Operator 0.9.5.1
-
Stylish 1.0.7
-
Tab Mix Plus 0.3.8.2
-
Xinha Here! 0.16
Disabled Extensions: [11]
-
Add-on Compatibility Reporter 0.4.1
-
Converter 0.9.3
-
Dublin Core Viewer 0.8
-
Java Quick Starter 1.0
-
Menu Editor 1.2.6
-
Microsoft .NET Framework Assistant 1.1
-
Multiple Tab Handler 0.5.2010012001
-
Password Exporter 1.2
-
RealPlayer Browser Record Plugin 1.0
-
Split Browser 0.6.2009110501
-
Weave Sync 1.0rc4
Total Extensions: 24
Things I use seldom or are evaluating are disabled by default, and enabled when I want to look at/use them.
Under Linux, I use a small subset:
-
All-in-One Sidebar 0.7.11
-
Greasemonkey 0.8.20091209.4
-
Image Zoom 0.4.2
-
MR Tech Toolkit 6.0.4
-
NoScript 1.9.9.42
-
Stylish 1.0.7
-
Tab Mix Plus 0.3.8.2
because the box running it is old, slow, and low powered. The FF config is as minimal as I can make it and still have it work as I prefer.
Quote:
i'm not even close to using chrome as my main browser (like you) but i like it for "casual browsing". although i admit i'm not liking it so much today. i'm not using the dev channel ; it's a "toy" browser for me, i'm not interested in putting up with quirks and crashes and bugs just to be on the bleeding edge with this one. (actually i'm rarely if ever interested in putting up with quirks, crashes and bugs to be on the bleeding edge, whatever the context, now that i think about it.  )
|
I got the dev channel build precisely to get extension support. Since it's not my production browser, I can live with the occasional quirk.
For that matter, I routinely use beta versions of FF. The base Mozilla code is solid and well developed, so betas aren't likely to make any messes I can't clean up.
______
Dennis