Memory leak after uploading files on Dropbox website

Hello, after updating to Windows 10 AU, I seem to notice a strange bug that when you upload a bunch of large files onto Dropbox website from Chrome, the ram slowly increases and last time I saw it, it was up to like 22% ram usage (32GB ram here). I closed Chrome to see if it decreases and it didn't. I also tried logging off and logging back in but it still remains. Only way to lower it was to restart pc. I've never seen quite a leak on the previous build.

Another thing that kinda bugs me was the Windows Defender. At first I thought Windows Defender might be the culprit so I tried disable cloud based protection, automatic sample submission, and enhanced notifications. Unfortunately, turing those settings up causes the app longer to start when I clicked the startup icon. However, clicking the app when I used the search function works fine. Before I turned those off, I can open Windows Defender easily when opened through the icon in the startup.

I had a feeling that the update is in teething stage, but I was hoping for someone to have any suggestions on what to fix these problems.

EDIT: Just to let you know, I tried updating the killer network drivers to the latest version on their website, not the motherboard website but I'm not sure if that one works or not.

Thanks! :)

Kinda need to bump this up. I ran the SFC /scannow and here's the results:

"Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log Windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging in is currently supported in offline servicing scenarios."

Here is the CBS file in the attatchment.

Still need help on this. After I run a full scan on Windows Defender, it shot up right to 20% ram usage and it doesnt go down afterwards. Please help me on this!

Well, I should've known that you guys need some clues on what is actually going on, here are the pics on whats happening today down below.

Today, I found that svc has a huge memory file around like 600mb of memory while the rest of them are between 90mb to 0.1mb in my processes tab in task manager.






I honestly tried everything and now this problem begins there. Can anyone have any answers to this?

Sorry, I don't see a problem. Memory usage is high, certainly. But there is a good reason for that. When there is plenty of memory available (and you have memory to burn) the memory manager will let processes use pretty much whatever they want. And why not? Memory was meant to be used, not sit idle. If there is a big demand for memory this usage will be automatically trimmed back as necessary. Of course with 32 GB that isn't likely to happen very often, if at all.

There is a persistent myth that says the more memory a computer uses the slower it will be. I saw web site that claims this is obvious. Actually the reverse is true. High memory does not cause performance problems unless it causes a shortage. And that is certainly not the case here.

High memory usage after uploading a large number of files is probably memory in the file cache. Task Manager will tell you nothing of this. Memory labeled as "Cached" does not include the file cache. Again this is not a problem unless there is a shortage, which there is not.

LMiller7 said:

Sorry, I don't see a problem. Memory usage is high, certainly. But there is a good reason for that. When there is plenty of memory available (and you have memory to burn) the memory manager will let processes use pretty much whatever they want. And why not? Memory was meant to be used, not sit idle. If there is a big demand for memory this usage will be automatically trimmed back as necessary. Of course with 32 GB that isn't likely to happen very often, if at all.

There is a persistent myth that says the more memory a computer uses the slower it will be. I saw web site that claims this is obvious. Actually the reverse is true. High memory does not cause performance problems unless it causes a shortage. And that is certainly not the case here.

High memory usage after uploading a large number of files is probably memory in the file cache. Task Manager will tell you nothing of this. Memory labeled as "Cached" does not include the file cache. Again this is not a problem unless there is a shortage, which there is not.

I understand what you're saying but did you look at the pic where the svchost.exe has a size of almost 700mb? That is definitely a leak unless if I'm mistaken.

In the old build, after i closed the most intense programs, the ram goes back to like 11.4% i.e around 3gb whereas the new build, the annuversary build where the ram never drops to that and that means there is a leak somewhere. Right now, the ram usage is currently at 5gb with nothing in the background. Tell me, is this not normal to you at all?

Sorry, but I still don't see a problem.

LMiller7 said:

Sorry, but I still don't see a problem.

Oh okay.
At least you saw the images I'd attatched to my previous post, right? Like, I honestly don't know if Microsoft change the memory management on the anniversary update or not, but all the cache memory stuff seems really new to me. I remember in Windows 7 where RAM gets filled up by applications and processes and once you closed all of it, the ram goes back to its smaller size. I'd honestly don't remember if the cache memory stuff was added on the previous windows 10 build which I honestly didn't care about that until now with the anniversary update build. That right there got me worried like if there's something wrong with the installation of windows 10. I used the Windows Update to download the anniversary update. It was pretty much smooth sailing until this one started.

By the way, I still have the problem where Windows Defender takes so long to load when you click on the windows defender icon on the startup. It works for the first time, but when you click on the windows defender icon again, it took like around 5 seconds then it launches. Launching it on the shortcut of Windows Defender didn't have that issue.

Also, check the CBS.log about the recent sfc /scannow one where it found corrupted files and sucessfully correct them. Can you check if its related to this?