Firefox Extensions Causing Memory leaks

[Abhas]

If your Firefox browser is running slowly, check out CyberNet's list of
memory-leaking extensions to see if you've installed any of the
extensions listed and if there's a simple solution to your memory drip.

* Adblock
Issue: Has been known to crash Firefox when trying to use Gmail Chat.
Fix: None available right now. It?s recommended that the extension be removed if you use Gmail Chat.
* All-in-One Gestures
Issue: Can cause Firefox to crash, and conflicts with the inline spellchecker on Linux and OS X.
Fix: None available right now. It?s recommended that the extension be removed if you?re using Linux or OS X.
* Fasterfox
Issue: Can interfere with website access, and problems may continue even if Fasterfox is removed.
Fix: Reset the defaults or start with a new profile in Firefox. Also make sure that you have prefetching disabled in the extension.
* Firebug
Issue: Causes excessive CPU usage
Fix: Disable Firebug when it?s not being used, or create a separate profile to use it in.
* ForecastFox
Issue: Memory leaks due to satellite imagery.
Fix: It?s recommended that the extension be removed, or you can install an older version without the satellite imagery.
* Google Browser Sync
Issue: Causes excessive CPU usage with GIF animations.
Fix: None available right now. It?s recommended that the extension be removed.
* Google Web Accelerator
Issue: Crashes Firefox when closing the browser.
Fix: None available right now. It?s recommended that the extension be removed.
* IE Tab
Issue: Memory leaks
Fix: It?s recommended that the extension be removed, or you can install IE View Lite as an alternative.
* Loki
Issue: Memory leaks
Fix: None available right now. It?s recommended that the extension be removed.
* Media Player Connectivity
Issue: Causes Unresponsive Script Warnings
Fix: None available right now. It?s recommended that the extension be removed.
* Mouseless Browsing
Issue: Causes excessive CPU usage
Fix: None available right now. It?s recommended that the extension be removed.
* SessionSaver
Issue: Memory leaks
Fix: Use Session Manager instead.
* Tabbrowser Extensions (TBE)
Issue: Slows down Firefox, conflicts with other extensions, and can stop Firefox from working.
Fix: It?s recommended that the extension be removed, or you can install Tab Mix Plus instead.


I came across this list, not sure if all is correct, but certainly worth looking at...

 

[KBC]

Try this Then,
*Starting Firefox in Safe-Mode
o Safe-Mode disables all extensions and themes and loads Firefox with the default template.If this method
uses continuously less memory a theme or extension is most likely responsible for the high memory
consumption.
o To run Firefox in safe-mode simply add the following parameter during startup "-safe-mode".

*Problematic Extensions
o Some extensions cause unwanted side effects.The Mozilla team is collecting information about those
extensions which can be looked up here.You can try the suggested workarounds to fix the problem or uninstall
the extension completely.
All the following tweaks can be achieved by typing in about:config in the Firefox address bar and entering
(part of)the bolded parameter into the filter field.

*Browser.cache.memory.capacity
o Controls the maximum amount of memory to use for caching decoded images and chrome (application
user interface elements).
o This determines if and how much system ram Firefox will use to cache itself.The element does not exist
and has to be created.The default value is set to automatic which means that Firefox uses a certain amount of
RAM by default.(values for Firefox 2.x)
+32 MB of RAM ->2 MB
+64 MB of RAM ->4 MB
+128 MB of RAM ->6 MB
+256 MB of RAM ->10 MB
+512 MB of RAM ->14 MB
+1024 MB of RAM ->18 MB
+2048 MB of RAM ->24 MB
+4096+MB of RAM >32+MB
o You can tell Firefox to use another value by creating the element in about:config and assigning a different
value (in KB)to it.It is also possible to turn this feature of by assigning the value 0 to it.This can greatly
decrease the performance of Firefox and is not advised at all.
o To reduce memory consumption reduce the amount of RAM that is assigned to Firefox.

*Browser.sessionhistory.max_entries
o Firefox 2.x saves the last 50 visited websites of a single session in memory which means that it could add up
quickly if you visit lots of content filled websites.
o Reduce the amount of websites that are stored this way to reduce the memory consumption.It does not
make a huge difference for most surfing habits to reduce the figure to 5 or 10.

*Browser.sessionhistory.max_total_viewers
o Automatically determine the maximum amount of pages to store in memory based on the total amount of
RAM.
o If you have 64 MB or Ram 1 page is stored in memory,2 for 128 MB,3 for 256 MB,5 for 512 and 8 for
everything higher than that figure.
o If you never navigate using the Back and Forward buttons in Firefox you can set this value to 0 to disable
the feature.
o Otherwise reduce the amount of pages stored in memory to make this feature use less memory.

*Config.trim_on_minimize
o This preference determines whether to allow Windows to reclaim memory from a minimized Mozilla
application.
o Set to True if you want to free up memory when minimizing Firefox.
o The value does not exist by default,simply create it and set it to true for better memory management.

 

[Highlander999]

Thanks guys, I'll check it out. i personally have found Firefox slow on occassions to connect to websites. Will check it out