Cesar Talledo

In case the problem is related to the interaction of `docker stats --no-stream` with Docker Desktop's resource saver mode, here's an ** unofficial ** Docker Desktop 4.30 pre-release build that...

> Stumbled upon this prerelease by chance and it fixes most the memory issues I had the past few weeks. 👍🏻 Thanks @luastoned for trying it out. Do you know...

Thanks @luastoned. > com.docker.cli, conhost.exe and docker.exe still take up 90% of the list in the Processes tab though. Mmm ... so you are still seeing lots of `com.docker.cli` processes...

Thanks @luastoned . > 45k process list entries, 42k are docker.exe, com.docker.cli Mmm ... let me see if I can repro with RAMMap. > I do have autoMemoryReclaim set to...

Hi @luastoned, > 45k process list entries, 42k are docker.exe, com.docker.cli I tried reproducing by starting DD 4.30.0 (146335) on my Windows hosts and leaving it idle for 5 minutes,...

Thanks @sparxooo for the response. > Do you wish me to update to the v4.30 version or remain on the version i'm on, just in case I can repro it?...

Hi @jd4u, Thank you very much for the additional info. > As you pointed to some extension, I disabled VS Code extension of Docker. The call to docker cli got...

Hi @jd4u, > There is no difference even with 4.30.0. The machine is restarted and initial ram usage was 3.6GB. Now 10+GB visible in screenshot. VS Code, Docker Desktop, Chrome...

Thanks @sparxooo and @jd4u for the additional info, very helpful. I am still debugging it but I agree it's not related to Docker Desktop's resource saver feature. @jd4u : can...

Hi @anton-filatov, Sorry you hit an issue, but thanks for reporting it. If possible, could you upload the [Docker Desktop diagnostics bundle](https://docs.docker.com/desktop/troubleshoot/overview/#diagnose)? That will provide us with even more info...