The problem has been reported by many, but not all users. This usually means the problem is not just in the app, but happens in some more or less rare combinations with something. Like I can see dozens of hreads referencing nvidia libraries (kinda unexpected) and obviously lots of Edge webplatform calls.
Unfortunately the memory leakage NOT happen on my computer, so I cannot participate directly.
Would you guys have chance to see what threads of Feeds (SearcHapp.exe) are most memory hungry? ProcessExplorer will help.
MP