locked
Extreme Memory Leak: Almost 100,000 Handles a Day. MEMORY_MANAGEMENT STOP Code

    General discussion

  • Hello,

    I am experiencing a HUGE memory leak working on Windows Developer Preview.

    According to task manager, the leak is about 100,000 handles a day. The OS stayed well @ over ENORMOUS 750,000 handles for 19 days and 20 hours and ended up with MEMORY_MANAGEMENT STOP code.

    The Task Manager shows the following:

     

    I used PowerShell and that's what I got:

    PS C:\Windows\system32> Get-Process | Where-Object {$_.handlecount -gt 10000}

     

    Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName

     

    ------- ------ ----- ----- ----- ------ -- -----------

     

    2568050 59 139204 539324 874 1 019,29 868 dwm

    Two and a half million handles for Desktop Window Manager!

    I do NOT have the kernel debugger so I can't just kd !analyze here.

    The OS created a minidump in %windir%\minidump.

    I overlooked the Action Center's settings and it showed the following:

    Do I understand it like OS has already sent the minidump to bugtracking servers? Or do I have to do anything to make it done?

    Additional:

    1. The OS natively boots in VHD.

    2. The OS is using nVidia video drivers and VIA audio drivers.

    3. In the System event log I see the following records:


    The previous system shutdown at 11:41:23 AM on ‎10/‎13/‎2011 was unexpected.

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001a (0x0000000000041790, 0xfffffa80064fecf0, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 101311-121056-01.

    An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): ''.

    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.


    The following boot-start or system-start driver(s) failed to load:

    3ware
     
    adp94xx
     
    adpahci
     
    adpu320
     
    amdsata
     
    amdsbs
     
    amdxata
     
    arc
     
    arcsas
     
    b06bdrv
     
    bfad
     
    dam
     
    ebdrv
     
    EhStorTcgDrv
     
    elxfcoe
     
    elxstor
     
    HpSAMD
     
    iaStorV
     
    iirsp
     
    intelide
     
    isapnp
     
    LSI_FC
     
    LSI_SAS
     
    LSI_SAS2
     
    LSI_SCSI
     
    LSI_SSS
     
    megasas
     
    MegaSR
     
    mvumis
     
    nfrd960
     
    nvraid
     
    nvstor
     
    ql2300
     
    ql40xx
     
    sbp2port
     
    SiSRaid2
     
    SiSRaid4
     
    stexstor
     
    storahci
     
    storflt
     
    storvsc
     
    viaide
     
    vmbus
     
    vsmraid
     
    VSTXRAID
     
    Wd
     
    WdBoot

    All the listed errors occurred after the STOP error.

    I understand that this is even not a beta and that it is normal to face the problems as such. The only reason I am asking is I want to help MSFT to figure out the possible root cause of the problem, that's it. If I knew how I could help, I would do my best to collect necessary info.

    I will be glad for any comments. Thank you.

     

    BTW: the new Task Manager is simply AWESOME!


    Well this is the world we live in And these are the hands we're given...



    Friday, October 14, 2011 7:14 AM

All replies

  • Do I feel like nobody else is experiencing problems with Desktop Window Manager application? Any clues?
    Well this is the world we live in And these are the hands we're given...
    Saturday, October 15, 2011 9:46 AM
  • Hey Exotic Hadron,

     

    You can check to see if the information has already been submitted by viewing your reliability history. You can do this by:

    • Enter your Start screen
    • Type Reliability
    • Click Settings in the left column
    • Click View reliability history

     

    Then select the day that this error occurred, which should have a red circle with an x in it. Then look at the information displayed below the chart. Each event will give the option to Check for a solution, View technical details, etc. under the Action column. Your error will probably display Check for a solution, go ahead and click that link. If any files need to be sent for that error they will be sent at this point, and you will be notified if there is a solution available yet.

     

    If you haven't already, it would also be helpful if you could submit this information using the Windows Feedback Tools from the Connect Site. If you’re an MSDN subscriber, the information on how to join the Connect program is included on the download page where you installed Windows Developer Preview.  There’s a link to the Connect site and an invitation code that you can click on to join using a Windows Live ID account. If you’re not an MSDN subscriber follow this limited use link to join the Connect program and then follow the steps here


    Steven
    Monday, October 17, 2011 10:09 PM
    Moderator
  • Thank you for your reply, Steven!

    The problem is that the Reliability Monitor DOES NOT show if it has sent the dump or not...

    Problem on the problem calendar:

    Description of the problem:

    I would love to send the dump file. Do I understand it right that I will be able to send it using the Windows Feedback Tools? Correct?
     
    Or is there any other way I could do that?

    Okay, I've got the Feedback Tool installed. How do I submit information about the fault?

    On the Identify your issue page I see Select area. What area do I have to choose to report a crash? I don't know what crash actually. I SUPPOSE it's because of memory leak.

    And I also know that I had

    STOP Error 0x0000001A: MEMORY_MANAGEMENT

    STOP error 0x1A means that a severe memory management error occurred. STOP code 0x0000001A may also display "MEMORY_MANAGEMENT" on the same STOP message.

    And I suppose that this is caused by a leak in WDM process.

    Steven, could you please guide me through here?

     


    Well this is the world we live in And these are the hands we're given...




    Tuesday, October 18, 2011 6:47 AM
  • Hey Exotic Hadron,

     

    Please submit this feedback in the following location:
    System performance and maintenance > Maintenance Troubleshooting > Performance issues

     

    Once you click Next you can describe the problems you have been experiencing. On the screen after that you will be able to click the Add button to attach the .DMP file that was created at C:\Windows\MEMORY.DMP.

     

    Hope that helps.


    Steven
    Friday, October 21, 2011 8:35 PM
    Moderator
  • I am still trying to find the reproduce steps, but it is pretty impressive that the computer did not slow down until the handle count of DWM exceeds 1.2 million.



    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP

    Friday, October 28, 2011 1:23 AM
  • I am still trying to find the reproduce steps, but it is pretty impressive that the computer runs normally until the handle count of DWM exceeds 1.2 million.



    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP
    Friday, October 28, 2011 1:24 AM
  • Which GPU do you both use? Do you use the latest drivers offered by WindowsUpdate?
    "A programmer is just a tool which converts caffeine into code"

    Tuesday, November 1, 2011 4:11 PM
  • Hi, Andre!

    I am using NVidia GeForce 9600GT. The driver is the latest one obtained from Windows Update.

    Driver version: 8.17.12.8516

    Date: 22.08.2011 1:01:00

    The driver has been WHQLed.

     

    Hi, Sheng!

    The leak is easily reproed on my rig. I just have to not reboot the PC daily. Approximate leakage in WDM is about 100,000 handles a day!

    As you see, after about 20 days of work the WDM leaked 2,500,000 (that is two and a half million!) of handles! That is fantastic! XP would've bluescreened on like total 300,000 of handles. I think, WDP memory management is simply fantastic!


    Well this is the world we live in And these are the hands we're given...
    Wednesday, November 2, 2011 6:11 AM
  • Hi Steven,

    Eventually my Windows Feedback Tool has blocked me from submitting defects. I've submitted a couple of defects and that's that I get now after trying to get past the Authentication page of the Send an issue report wizard:

    The given Live ID does not have permission to submit bugs for the Connect form defined for Feedback Tool, or the service is unavailable.

    What could it mean?

    Could you please help me here?

    Thank you.


    Well this is the world we live in And these are the hands we're given...
    Wednesday, November 2, 2011 8:04 AM
  • my computer does blue screen quite frequently for other reasons (e.g. when I plug in the network cable or when I add a projector), so I haven't able to reproduce the problem.

    The following is signature, not part of post
    Please mark the post answered your question as the answer, and mark other helpful posts as helpful, so they will appear differently to other users who are visiting your thread for the same problem.
    Visual C++ MVP
    Monday, November 7, 2011 5:52 PM
  • Okay, I've got 10,5 mln handles per process today! Anyone to beat the record? Ha-ha. This is fantastic, I can't believe that memory management is now that perfect!
     
    Get-Process | Where-Object {$_.handlecount -gt 10000} | Format-List
    Id : 936
    Handles : 10434043
    CPU :
    Name : dwm
    Well this is the world we live in And these are the hands we're given...

    Thursday, December 22, 2011 12:21 PM
  • How to troubleshoot a handle leak?


    "A programmer is just a tool which converts caffeine into code"

    Thursday, December 22, 2011 1:14 PM
  • Oh, that's a very interesting article, thanks for sharing. Seems to be what I am needing now. When I am a layman in all that debugging, I'll try to tame that WinDbg. Thank you!
    Well this is the world we live in And these are the hands we're given...
    Thursday, December 22, 2011 8:25 PM
  • I'm seeing the exact same problem (dwm.exe leaking tons of handles) with Win8 Dev Preview running on a Fujitsu T4410 touch tablet.
    Marius Dumitru
    Saturday, February 4, 2012 10:12 PM
  • Do you use the latest Intel graphic card drivers?
    "A programmer is just a tool which converts caffeine into code"

    Sunday, February 5, 2012 1:33 PM