ManagedClient Memory Leak

This happened in the company I work for. They use VMware's Workspace One Intelligent Hub. The latest 22.05 version of Workspace One Intelligent Hub solved the issue for us.

I got 22.05.1 and it seems to be working fine now, thanks!

Hello BIG_Seth,

Is your Mac being managed by a business/school/enterprise?

It may help to try launching the Mac into safe mode for a period of time, just to see if it still happens here. Details on what this entails and how to perform it can be found here: Start up your Mac in safe mode - Apple Support

It can also help to try manually force closing apps that are open, after saving any work in them (Command-Q, or Command-Option-Esc for Force Quit menu), and watch the Activity Monitor to see if the process in question goes away when a particular one is closed, to help see which it's linked to.

Cheers.

For others that discover this post, you can get Workspace One Intelligent Hub 12.05 from https://getwsone.com

bryanfrombc wrote:

I am on 22.04 and also have the leak :(

Get 22.05 directly via

https://getwsone.com

We appreciate you clarifying this for us, BIG_Seth,

Are you the administrator of the managed Mac? If not, we'd suggest that you contact the administrator as this behavior may have to do with the device management.

If you are the administrator, we'd suggest that you reach out to Apple Support directly to investigate this further with you. You can find their contact details here: AppleCare Professional - Help Desk Support - Apple

Take care!

BIG_Seth wrote:

ManagedClient is increasing 400-500 MB of RAM usage per hour until it reaches many GB in size and the machine starts to suffer.

Killing the process just starts it all over again, and I have to kill it several times daily.

What is causing this? How can we solve?

Is this machine bound to some enterprise/ MDM or such?

are you administrating multiple devices or this is an isolated issue?

May I know which MDM platform you are using? I have the same issue on my working laptop too.

Wow I think that's likely to be the cause, we are using 22.03.0 version ws1 too in my company.

Thanks bro for your advice, we got same reply from vmware support about this too.

I am on 22.04 and also have the leak :(