Under review

High Memory Usage on MacOS

zach 3 years ago updated by flightdelta 1 year ago 11

I'm noticing on Mac memory usage of the guest client frequently exceeds 2GB while idle (no host client connected). Is this intentional? I understand the guest client is Java-based, is it possible to tweak the memory pool size of the Java VM?

The version of the client I'm seeing in my ScreenConnect console is 6.6.18120.6697.

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:
Not a bug

So we've looked at this a few times and basically it comes down to java's relatively inefficient garbage collection.  While it's true that capturing a dynamically changing screen does use a decent amount of memory it's really due to how java allocates chunks in pretty large sizes (sometimes up to ~500MB) and only deallocates them when usage is below a pretty large threshold.  This means our client could be using 501MB but it's allocated 1GB.  Supposedly they've improved this within Java 10 but I haven't had a chance to investigate this in order to confirm.

I'll bump the task to take another look at how Java 10 has (or has not) improved this.

Did this ever get looked at? Was there a resolution confirmed for this? We have a similar issue running with a client at the moment where the RAM is being eaten by ConnectWise Control with no explanation why.

The problem still exists on Screen Connect 6.9.21870 with Java 10 installed.

Hi All,

The fix for this issue was just released in our 19.6 canary build.

Hi - the memory usage starts around 70MB and grows to 2gb through out the day on my iMac. I kill the process once in the morning and sometimes during the day. Not the right solution, but thinking of writing a script that will do it automatically. What is causing it? I don't see this issue on WinOS. 


Are you seeing high usage during an active session, or is this high memory usage during an idle period?

This AM it was up to 540MB. Usually I find it higher. It's my work computer. I remoted in to see if anything changes and it dropped to 230. not sure if it got moved to compressed mem. I can keep an eye on that. ran jvmtop/jmap but can't get stats on the process

Right before sending OS purged the compress mem


Caitlin, more info for your research. Please let me know what you find

After remoting in

After a process kill

Under review

Thanks for the additional info! I'll pass it along.

Hi FixOn3, 

We've taken a look at your recent reports, but it appears what Scott reported 2 years ago when this was marked as "not a bug" still rings true. The issue isn't that we're using a large amount of memory, just that Java isn't great at recycling memory or at least showing what's available.