Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

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

  • 1 réponse
  • 23 ont ce problème
  • 1 vue
  • Dernière réponse par 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.

Modifié le par Tinium

Toutes les réponses (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.