This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

Causes windows 7 desktop window manager (wdm.exe) to use large amounts of memory

  • 1 respuesta
  • 23 tienen este problema
  • 1 visita
  • Última respuesta de 64punisher46

Tinium
Tinium
more options

Whenever I have Firefox4 open, it causes dwm.exe (Windows desktop manager) to use large amounts of RAM - It starts at about 100MB, quickly increasing to about 1GB over 20 seconds, then dropping back down to 100MB and so on. It does this continuously while Firefox4 is open, with the occasional "Your computer is running slow" message being shown by Windows.

Update: Only occurs when browser isn't on the primary display on a multi-monitor setup.

Whenever I have Firefox4 open, it causes dwm.exe (Windows desktop manager) to use large amounts of RAM - It starts at about 100MB, quickly increasing to about 1GB over 20 seconds, then dropping back down to 100MB and so on. It does this continuously while Firefox4 is open, with the occasional "Your computer is running slow" message being shown by Windows. Update: Only occurs when browser isn't on the primary display on a multi-monitor setup.

Modificadas por Tinium el

Todas las respuestas (1)

64punisher46
64punisher46
more options

I had the exact same problem. DWM would use massive amount of memory when Firefox 4 was open on my secondary display, especially when scrolling with the mouse wheel. It would use so much that Windows 7 (8GB RAM) would turn off Aero. Going into Options>Advanced>General and unchecking "use hardware acceleration" fixed the issue. Of course now I can't take advantage of any hardware acceleration.