3 ms·

Preemptive apologies for this glorified "it's nice to hear it's not just me" of a post. To let you skip the anecdote if you don't care, I'd be very curious if

Preemptive apologies for this glorified "it's nice to hear it's not just me" of a post. To let you skip the anecdote if you don't care, I'd be very curious if someone can answer _why_ this happens. Earlier this week I was running into Very Strange errors coming out of some deep libraries in one of my hobby services. Nothing was specifically failing but things were going very slow and vomiting a bit. I observed that I had over 25g of active Ram (Typically idle at ~8g) and some absurd amount of paged data too. Even after killing almost all non-system running processes I was sitting at ~20g total, including a 10g nonpaged pool and 6g process private. On reboot, and for the week since? 8g. (On Win10)

aybassiouny 8y ago
I recommend to do more debugging next time and see which process exactly is costing you all this. It sounds like a classic memory leak - those can be triggered nondeterministically. Maybe try some of the tools suggested here https://mahdytech.com/2019/01/05/task-manager-memory-info/ https://mahdytech.com/2019/01/05/task-manager-memory-info/
- existencebox 8y ago
  That's the fascinating part; I followed _that specific_ top google result plus a few others, dug around in RamMap, but couldn't find anything to finger any particular process as owning all the consumed Ram. Admittedly a bit out of my league in terms of system level debugging here, but all of the typical culprits said "everything looks normal except you actually have like no ram free," and given that it was impeding my primary work machine + that I had no track record of these symptoms occurring before, I eventually resigned myself to a reboot.