If you have used Firefox (Chinese name: Firefox), then your first impression of it must be that browsing speed is very fast! Because it uses the "first download web page text structure, then download images" browsing method by default, and IE uses the "web page text and image download at the same time" browsing method. However, when you install the commonly used plug-ins (also known as "extensions"), your impression of Firefox may gradually change. The original lightweight fox suddenly becomes a fat fox with "eatlessness"! When you open the "Windows Task Manager" actually found it had "eat" out why more than 300 MB of memory ......
never feed the foxes do not eat? Why
original footprint very small memory footprint of Firefox has become the culprit it? It turned out to be a horrible "memory leak"! Many people know that when writing a program, it is necessary to allocate a memory area for the data to be used, and then write the data into the memory. When the data is not needed, the divided memory area is recycled. "allocation of memory", but sometimes because of the negligence of programming or the error of the compiler itself (programming negligence is equivalent to the production of the product before the design is problematic, and the compiler's own error is equivalent to the correct design is faulty The machine produced an unqualified product), resulting in the memory area that was divided out has not been recovered, so even a small "memory leak" will eventually lead to the complete exhaustion of system resources! Since Firefox did not have such a serious memory footprint before installing various plug-ins, we judged that the memory leak of Firefox may be caused by the plug-in! In the Mozilla official and Firefox technical forums, I finally found all the reasons that would cause Firefox to over-commence.
destroy pathogenic five "pathogen"
number one pathogen: Adblock plug
cause of the disease: it is used to Maxthon users will definitely install ad blocking plugins, but Adblock, the most widely used ad blocking plugin, has serious memory leaks in Firefox 1.5.
Treatment: Uninstall Adblock, install Adblock Plus and upgrade to the latest version. Select the menu "Tools → Extensions", select "Adblock 0.52.056" in the pop-up "Extension" window (the version number may be slightly different), click "Uninstall" (see Figure 1), close Firefox and then re-open after completion.
Adblock Plus link: https://addons.mozilla.org/extensions/moreinfo.php?id=1865&application=firefox
No. 2 pathogen: Java
cause of the disease: older versions of the Java runtime Firefox memory usage leads to serious.
Treatment: Java users should upgrade to Java Runtime Environment 1.5.0_06 (or above), and also close the "Java Console" in the Java Control Panel to reduce memory usage.
Three pathogens: Adobe Reader
cause of the disease: the old version of Adobe Reader using too much memory.
Treatment plan: Adobe Reader 6.0/7.0 will take up a lot of memory, please upgrade to Adobe Reader 7.0.5, if you disable Adobe Reader plugin in Firefox can also reduce memory usage, but it is recommended to keep (otherwise every time It is inconvenient to download PDF files.
IV pathogens: a fixed size cache
pathogenesis: Firefox default divided into a memory area for the Web cache.
Treatment plan: By default, the cache size of Firefox is not fixed. Setting the size of the cache can reduce the memory consumption. The setting steps are as follows:
Open in the address bar of Firefox webpage. About:config" (without quotes) enters the Firefox advanced settings state (see Figure 2). In the advanced settings list, set "browser.cache.memory.capacity" here to set the cache size according to your own situation (double click to enter the edit state) ), users of small memory can consider setting "browser.cache.memory.enable" to False to completely disable the in-memory page cache, but this will slow down Firefox.
V pathogens: fast forward, rewind
cause of: fast forward and rewind speed in order to ensure a certain amount of memory space used.
Treatment plan: Go to the advanced settings of "about:config" and set "browser.sessionhistory.max_total_viewers" to 0.
Tips
we can to further optimize Firefox to get a smaller memory footprint, such as in the Advanced Settings "config.trim_on_minimize" is set to true energy To make Firefox free up memory when it is minimized, installing the NoScript plugin to disable JavaScript can save script usage and so on.