When Dolphin is started, it reads from/generates the cache and loads the list of available titles in the UI window. When doing this, if you open the Windows Task Manager you'll see that the Paged Kernel Memory and System RAM usage have increased by a large amount. Memory that the OS will NOT release even after Dolphin is closed (!).
Even worse, each time you use the "Purge Cache" option to rebuild the cache, it amplifies the Paged Kernel Memory leak (almost doubles the amount of RAM lost).
Now this gets really bad when testing multiple buids of Dolphin for regressions or benchmarking.
Each build started adds even more memory to the Paged Kernel pool.
With multiple versions and cache purging, the total amount of memory lost due to this leak can reach up to 1 GiB or more. Memory that won't be released unless you REBOOT the OS.
Is this issue ever going to be fixed for the current Wx UI? What abut the Qt UI rewrite? Is the next-gen Qt List finally going to put an end to this long-standing issue?
Even worse, each time you use the "Purge Cache" option to rebuild the cache, it amplifies the Paged Kernel Memory leak (almost doubles the amount of RAM lost).
Now this gets really bad when testing multiple buids of Dolphin for regressions or benchmarking.
Each build started adds even more memory to the Paged Kernel pool.
With multiple versions and cache purging, the total amount of memory lost due to this leak can reach up to 1 GiB or more. Memory that won't be released unless you REBOOT the OS.
Is this issue ever going to be fixed for the current Wx UI? What abut the Qt UI rewrite? Is the next-gen Qt List finally going to put an end to this long-standing issue?