Sonar (Kontakt) Memory Issue with Kontakt Window open. {SOLVED}

Hi,
 
Discovered a unique issue. Not sure if it's a Kontakt issue or a Sonar issue. I've reported it to NI too.
 
I'm using the latest version of Kontakt / Sonar.
 
If a Kontakt window is left open and I Alt-Tab out of Sonar and do something in Chrome or another application, after a period of time, memory usage goes up and up. I tend to have multiple applications running on the studio computer at all times due to working in games, so I'm Alt-Tabbing/switching programs frequently.
 
Closing the Kontakt window immediately solves this, though closing the window takes longer than usual. This is due to the emptying/unloading (forgive the terminology) of whatever RAM usage 'leaked'.
 
Specs are i7 7980X, 128 GB RAM, OS is an M2 SSD, samples are 5 x 4 TB Samsung EVO SSDs. Windows 10 Pro.
 
Any thoughts would be appreciated. It's not a major issue, and it is solvable, but it's never happened before. It's either an issue with the new Kontakt, or Sonar.

That was my first thought, too, but I don't think that's a factor. Gareth says he can alleviate the symptom by closing the Kontakt UI. Background loading would continue even if the UI is closed.
 
I would let it run that way for a while and see if the memory reduction continues indefinitely or eventually stops.
 
Increasing memory usage isn't the same thing as leakage. The former can happen just because software is buffering a large amount of data (such as a sample library). The latter occurs when you close a program and some of the memory it had allocated while running is not relinquished.

Forgive the incorrect use of terminology.
 
I should have mentioned, this went all the way to the extreme. I left my computer on overnight, and when I came back in the morning, the memory usage was up to >90% in SONAR. I'd left a Kontakt window open on the screen. This shouldn't be happening.
 
Background loading isn't it, even the longest loading libraries such as Joshua Bell Violin or Hans Zimmer Pianos load in seconds, rather than minutes. And regarding this, we're talking about hours of 'something' going into the RAM.
 
I've made a video of the issue which you can see here.
 
Direct link - https://gareth-coker.box....79ibg9l0xklhorjlq5.mp4
 
This is a very very light project, only 4 NKIs loaded. The RAM goes up while playing, while not playing. And then at the end, when I close the 2 Kontakt windows, it goes down from 5 GB to 4 GB usage. If I had the time/patience I could have waited an hour and it would have gone up and up, and then I'd close the window and the RAM would go back from whatever ridiculously high usage it would be after an hour, back to the 4 GB.
 
Stumped me. As I said, easy to solve. Just remember to close all windows. It does not appear to be an issue with other VSTis. I wonder if anyone else can recreate this issue. It's a very odd bug that I can live with, but it's not one I've encountered in all my years using SONAR.