Memory Leak: Difference between revisions
(memory usage) |
|||
Line 7: | Line 7: | ||
===Functional work-around=== | ===Functional work-around=== | ||
First, download the Firefox [[SessionSaver]] extension when Firefox is functioning normally. When the memory leak error occurs, go to [Ctrl+Alt+Del] "Task Manager -> Processes" and identify the "firefox.exe" process. Terminate the process, ignoring the warning message. Wait for the process termination to execute fully—usually in 5 - 10 seconds. Re-load Firefox. The Session Saver will bring back all the Firefox tabs from the terminated session. The memory leak error will have been terminated. If it re-occurs, repeat the work-around. | First, download the Firefox [[SessionSaver]] extension when Firefox is functioning normally. When the memory leak error occurs, go to [Ctrl+Alt+Del] "Task Manager -> Processes" and identify the "firefox.exe" process. Terminate the process, ignoring the warning message. Wait for the process termination to execute fully—usually in 5 - 10 seconds. Re-load Firefox. The Session Saver will bring back all the Firefox tabs from the terminated session. The memory leak error will have been terminated. If it re-occurs, repeat the work-around. | ||
===Memory usage=== | |||
Typical Firefox memory usage reported by Windows is around 50-100 MB, with virtual memory usage at 100-150 MB. If you experience substantially more usage than this, then you may be experiencing a memory leak, or you may just be viewing pages with large amounts of data. To attempt to free memory, you can try [[Editing configuration|setting the pref]] config.trim_on_minimize to true, and then minimize all Firefox windows. At this point, memory usage should drop to under 10 MB, while virtual memory usage should stay the same. If you then restore the Firefox window, memory usage will return back to its previous amount over time, but may be somewhat less than when you started. | |||
[[Category:Issues (Firefox)]] | [[Category:Issues (Firefox)]] |
Revision as of 23:27, 9 November 2005
Description of error
For some users, Firefox routinely generates a memory leak error. The problem could be due to the program itself, to an infinite loop in a poorly constructed Web site, a Firefox theme or extension, or a plugin. The error often occurs after Firefox has been used for prolonged periods of time, after extensive use with heavy downloads of images or other files using cache, or after extensive use with multiple tabs. When it occurs, the memory leak is visible in [Ctrl+Alt+Del] "Task Manager -> Processes" , where memory usage will be seen to increase dramatically even though Firefox use itself is dormant or static. If an infinite loop is encountered, memory use may increase very rapidly until all computer memory is consumed. Clearing the Firefox cache does not reduce memory usage. Usually, the dramatic memory use increase will continue unabated. Increasing memory size, or closing tabs, does not alleviate the error. Exiting Firefox in a normal way will usually be ineffective as, by this stage, Firefox will have hung, or will shortly hang, in this error state.
Prevention and troubleshooting
Users should first update to the most recent version and make sure all addons are properly updated. If the problem persists, the extensions can be disabled in safe mode for troubleshooting. Occasionally a new profile may be necessary. Follow the steps in the Standard diagnostic. In some cases it may also be necessary to disable a plugin or to reinstall Firefox in a new directory. If none of these steps solves the problem and the problem is not due to a particular Web site, closing and reopening Firefox will reduce memory use to normal values.
Functional work-around
First, download the Firefox SessionSaver extension when Firefox is functioning normally. When the memory leak error occurs, go to [Ctrl+Alt+Del] "Task Manager -> Processes" and identify the "firefox.exe" process. Terminate the process, ignoring the warning message. Wait for the process termination to execute fully—usually in 5 - 10 seconds. Re-load Firefox. The Session Saver will bring back all the Firefox tabs from the terminated session. The memory leak error will have been terminated. If it re-occurs, repeat the work-around.
Memory usage
Typical Firefox memory usage reported by Windows is around 50-100 MB, with virtual memory usage at 100-150 MB. If you experience substantially more usage than this, then you may be experiencing a memory leak, or you may just be viewing pages with large amounts of data. To attempt to free memory, you can try setting the pref config.trim_on_minimize to true, and then minimize all Firefox windows. At this point, memory usage should drop to under 10 MB, while virtual memory usage should stay the same. If you then restore the Firefox window, memory usage will return back to its previous amount over time, but may be somewhat less than when you started.