VMware Horizon View Client 4.4.0 + Windows 10 (1703) = massive memory leak

In case anyone else sees this behavior, I thought I'd post this here. It caught me by surprise, and I couldn't find any solution readily available.

I run a small VDI farm for myself and a few other engineers, and I came across an interesting issue. When I upgraded my home desktop to Win 10 1703, I started getting out of memory errors. I tried chasing them down for 3 days.

I reinstalled my desktop (I just built a Ryzen build, I was concerned about craziness in the update) and i had the same issue. I switched to my tablet that also had 1703, and decided the only common thing was VMware. I removed it from the tablet, and it went back to working fine. One I removed it from the desktop, my memory problems went away.

The symptom was an ever increasing amount of committed memory. My commit charge grew to 100% within a few minutes of booting, and it was just a matter of time before my page file had enough.

The real pain was that I couldn't see what was using the memory. Process Explorer wasn't showing me what the issue was. I think it was an associated service that gets installed with the client.

I've switched to the UWP client for now, which sucks...but at least I'm not leaking memory anymore.