How to Fix for Firefox memory leak problem on Windows

This seems to help out with the memory usage quite a bit. Generally, when you minimize a window the memory usage goes way down because that application isn’t active. Unfortunately, Firefox by default doesn’t adhere to this behavior. Here’s how to force it to.

Type the following into your address bar in Firefox:

about:config

You will see a window that looks similar to this:

You will want to right click anywhere in the window, choose New, Boolean, and enter in the following text:

config.trim_on_minimize

To change the value you can either doubleclick, or right-click and choose Toggle. You will have to restart Firefox, but after you do, you should notice the memory usage go way down whenever you have Firefox minimized.

Update: You will want the value to be set to True in order for this to work.

How to fix Firefox 3 Memory Leak problem

Recently, I have very big problem with my Firefox browser. Few minutes after starting of Firefox application, my Firefox become too slow for surfing, all open applications freeze for two or three seconds after every my click. I noticed that Firefox.exe take up a big part of my computer memory. After reading several forums on the net, I find how to fix this “Firefox memory leak” problem.

Just follow these simple steps to get your Firefox memory usage under control. The solution was in ”about:config” Firefox hidden configuration options.

  1. Get the main configuration screen by putting “about:config” in the browser’s address bar.
  2. Right click on the page and choose New then Integer and create an integer called “browser.cache.memory.capacity”. Set it to a low number (I use 16384 – that means 15MB). This controls how many kilobytes of memory are used for the browser’s cache.
  3. In the Filter of “about:config” page (top of the page) put “browser.cache.disk.capacity”. Set “browser.cache.disk.capacity” (right click – Modify) to between 5000 or 15000 (I use 15000). For example: if you have 128MB to 512M use 5000, if you have 512BM to 1GB of RAM use 15000. This controls how many kilobytes of memory are used for the browser’s cache.
  4. Configure Firefox to swap memory to disk when minimized. In the Filter of “about:config” page (top of the page) put “config.trim_on_minimize”, Right click on the page and choose New then Boolean and create an boolean called “config.trim_on_minimize”. Set it to true. This mean – when you minimize the firefox window it will free up memory.
  5. In the Filter of “about:config” page (top of the page) put “network.prefetch-next”. Set “network.prefetch-next” to false. Network link prefetch will download all pages with the rel=”prefetch” tag, with false you avoid that downloading.
  6. In the Filter of “about:config” page (top of the page) put “browser.sessionhistory.max_total_viewers”. Set it to low number. I set it to 6. This controls how many pages of history are kept in the back/forward buttons.

Restart Firefox and that’s it! Now, your Firefox and your computer will be much faster and you are ready for faster surfing. Enjoy!

What is dwm.exe And Why Is It Running?

You are no doubt reading this article because you are wondering why this dwm.exe process is taking more memory than you think it should, and you are curious what it does. Thankfully for you, we have the answer.

So What Is It Anyway?

Desktop Window Manager (dwm.exe) is the compositing window manager that gives you all those pretty effects in Windows Vista: Transparent windows, live taskbar thumbnails (that you can resize now), and even the Flip3D switcher that you can disable and replace with Switcher.

image

What happens in Vista is that applications write the picture of their window to a specific place in memory, and then Windows creates one “composite” view of all the windows on the screen before sending it to your monitor. Because Vista is keeping track of the contents of each window, it can add effects when layering the windows such as the transparency we’re all used to, as well as the live preview thumbnails.

The benefit to using this approach is that Windows Vista can utilize the hardware acceleration features in your video card to create very smooth animations for minimizing and restoring, and even for the transparent effects.

What about Memory Usage?

If you open up Task Manager, you can see the dwm.exe process in the list, typically taking somewhere between 30-50MB of memory in my testing:

image

The size of the DWM process is controlled by the number of windows that you have open, since each window requires a buffer in memory to store the contents of the window. If you have a large number of very large windows open, DWM will use more memory.

The benefits of using a compositing window manager are worth that relatively small amount of memory under most circumstances.

Does Switching to the Vista Basic Theme Turn it Off?

The short answer is no, just switching to the Vista Basic theme will not turn off DWM, but it will reduce the memory usage a great deal.

image

How do you switch to Vista Basic? Just right-click on the desktop, choose Personalize, and then Window Color and Appearance:

image

Click on classic appearance properties at the bottom:

image

Then choose Windows Vista Basic and click the Apply button:

image

Note that I’m not recommending switching to the Basic theme, just explaining how to do it.

So How Do I Turn dwm.exe Off Then?

Note that I don’t recommend turning this off unless you are playing games in fullscreen mode, and even then it likely won’t help increase speed.

The only way to get rid of the dwm.exe process is to stop the service from running. Open up Services from Control Panel or the start menu, and then find the “Desktop Window Manager Session Manager” service in the list, and click the stop button. Note that you will be switched to the Vista Basic theme when you click the button.

image

To permanently disable it, double click on the item and select Disabled from the “Startup type” drop-down:

image

If you want to use the command line instead, you can open an administrator mode command prompt and use one of these commands:

Stop Service net stop uxsms
Start Service net start uxsms
Disable Service sc config uxsms start= disabled
Enable Service sc config uxsms start= auto

By now you should understand what the process does… do you really still want to get rid of it?