Preface: I did not take screenshots, but I’m more than happy to add some if it helps.
I think this is the root cause of this issue. I built a new rig, installed SignalRGB for the first time on any rig, and for some reason after ~24 hours of uptime task manager would say that my entire 48GB of ram was in use, even though there were no running processes.
Sparing the countless pointless rabbit holes, eventually I checked RAMMap and noticed that page tables were consuming an insane amount of RAM, so checking the process list in that I noticed thousands of cmd.exe and tasklist.exe processes that were open (each holding a 32kB page table). Given that I don’t have a whole lot of things installed, I figured given tasklist was present it was probably the auto conflicting process killer in SignalRGB that was leaving these processes open. I turned the auto killer off, and now my memory issues are solved. Maybe some force killing of the spawned processes is necessary here.
