Custom Resolution Utility (CRU)

[Squall Leonhart]

on nVidia drivers, Restart64 causes a race condition inside the desktops Explorer.exe process which results in a resource leak , this condition is not triggered through toggling the driver state manually in device manager.

under this condition, both video memory commit and working set grow in the following events

* Opening the start menu rapidly
* Turning a display on and off (with displays that are treated as disconnected when turned off, like tv's)
* changing the windows advanced performance settings

The first is only a few hundred MB's at a time, the second 2 can be gigabytes of memory each time you perform the action.

I suspect the cycle is too fast for the UMD state to complete unloading, else its crapping up the shell animations / dpi change automation.

after using Restart64, i can power cycle my tv until the kernel runs out of memory and display driver fails to recover from a TDR,

I caught this most recently when i noticed 14GB's memory and 5GB's of vram consumed by Explorer.exe, after Ryujinx's Vulkan failed to start correctly (Nvidia drivers don't handle vulkan overcommit at all)