But when you used the plug-in (also known as the "expansion") are installed, you may have the impression that Firefox will be gradually changed the original light of all of a sudden it will become a fox "uncontrolled eating," the fat fox ! When you open the "Windows Task Manager" after it was found to have "to eat" lost more than 300 MB of memory ... ...
Why not feed the fox always full?
Originally occupied by the resources of Firefox can be a very small memory footprint of the culprits then? It was horrible, "memory leak"! It is well known in the programming, which will be used to be allocated a piece of data memory area, and then write this piece of data in memory, these data do not, they go out into the memory to the recovery of the region into " The allocation of memory ", but sometimes because of negligence or programming compiler's own error (negligence on the procedures for the preparation of the equivalent of pre-production product design issues there, and the compiler's own error is equivalent to the right in a design fault The machines produce a sub-standard products), led to the division of memory out of the region have not been recovered, so even if only a very small "memory leak" that they would eventually cause the system resources exhausted! Firefox due to a variety of plug-ins installed in the former did not have been so severe memory footprint, so we to judge: Firefox's memory leak problem may be caused by plug-ins! Mozilla and Firefox in the official technical forums, finally found all the Firefox lead to excessive memory footprint.
The eradication of the disease five "pathogen"
Pathogens number one: Adblock plug-in
Cause: used to Maxthon users ad will certainly block the installation of plug-in, but the most widely used advertising to intercept Adblock plug-in version of Firefox 1.5 in serious memory leak problem.
Treatment: uninstall Adblock, and the installation of Adblock Plus upgrade to the latest version. Select the menu "Tools → expansion" in the pop-up "expansion" window choose "Adblock 0.52.056" (version number may be slightly different), click "uninstall" (see Figure 1), after the completion of the re-closure of the Firefox open .
Causes: the old version of the Java Runtime Firefox lead to a serious occupation of memory.
Treatment: Java users to upgrade to Java Runtime Environment 1.5.0_06 (or more), and Java in the Control Panel to close "Java Console" can also reduce memory footprint.
Three pathogens: Adobe Reader
Causes: the old version of Adobe Reader takes up too much memory.
Loading...
