MAJOR memory leak on Windows 10 Pro x64 [Killer Network Issue]

**********************************************************************
UPDATE

The issue turned out to be the Killer network card. Download the base drivers (without killer features) from their website, and then spend some countless hours of uninstalling the Killer Network Manager (that was basically everywhere).

Also, set:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Ndu\Start to “4”.

After that, reboot computer, issue solved.

Have now verifyed and I see no larger usage than 2.5 GB, even when downloading about 150GB games.
**********************************************************************

ISSUE

Steam does not release back memory to the operating system after having written data downloaded while installing game data.

Im not entirely sure if this is a issue just in beta client, or if this is a issue that is also present in stable. Regardless, the issue should be fixed anyways.

A second issue, related to the first, is that Steam does not release memory allocated when quitting. This is a pretty severe issue, since this means that this memory will never be reused again, since the new Steam process will have a another process ID and no longer access the claimed memory.

OS
Windows 10 Pro x64 (with 32GB ram)

STEPS
Have a large game library with large parts not installed
Download every game in your library.
Have resource viewer up and notice how Steam just eats and eats more and more memory. However, it does not actively use the memory that it has claimed, so it will still look like Steam is using 85MB of memory.
Quitting steam also wont release the claimed memory.

RESULTS
Steam just eats and eats more memory. Regardless of how much memory you have in your computer, Windows will soon complain that theres not enough RAM on computer, especially if you have your paging file turned off.

EXPECTED
Steam should release back memory to the operating system after having written all game data to disk.
If this is not possible due to technical constraints:
If theres more games to download in queue, it could atlease reuse the RAM memory it did claim for the previous game to download the next game, so the maximum memory leak is contained to the size of the largest game in queue.

12. pro. 2015 v 11.16

Naposledy upravil Sebastian Nielsen