none
Memory leak (severe, can eat gigs of ram) RRS feed

  • General discussion

  • Reproduction steps:

    1. Note memory usage of procexp[,64].exe
    2. Open properties of a running program
    3. Go to the security tab of the new window
    4. Click the permissions button
    5. Click the advanced button
    6. Close all popup windows and look at memory usage of procexp[,64].exe again and notice several gigs have been suddenly eaten and not freed.

    Repeating step 5 over and over will result in a steady growth of memory, indicating it isn't reusing the data it has already.


    • Edited by Chris S-R Sunday, December 29, 2019 11:46 AM
    Sunday, December 29, 2019 11:41 AM

All replies

  • I have reproduced the same steps and verified this to be true. Please fix this bug. This is on Win 10 ver1803  PE 16.30

    Thanks

    Monday, December 30, 2019 12:22 PM
  • True..

    as a quick workaround you can use RamMap and "Empty" "Working Sets"..

    This will release the memory from Process Explorer working set..

    HTH
    -mario

    Tuesday, December 31, 2019 4:48 PM
  • Could I confirm that this is definitely there in 16.30 and not a regression that was introduced in 16.31? The reason I ask is that for 16.31 I made a major change to the way that we manage GDI resources to resolve a GDI exhaustion issue and I wanted to eliminate this as a possible cause first

    MarkC (MSFT)


    • Edited by markc(msft) Thursday, January 2, 2020 8:51 AM
    Thursday, January 2, 2020 8:51 AM
  • Hi Mark,

    it happens on 16.30 too.. no regression.. has always been there probably.. I've never noticed before also because I rarely open that window..

    HTH
    -mario

    Thursday, January 2, 2020 10:00 AM
  • Thank you Mario and happy new year to you. I have added this to our backlog and will take a look.

    Thursday, January 2, 2020 10:25 AM
  • Happy new Year!!

    -mario

    Thursday, January 2, 2020 10:35 AM
  • As a software dev myself, you would think I would know better than to not include the version that I'm running and found the bug in, which is 16.30.
    Friday, January 3, 2020 7:52 AM