I've been noticing that Multiplicity periodically utilizes a significant amount of CPU resource on secondary after a period of time with a KVM connection. This happens on the 'remote' machine, not the primary where I am running the KVM window, and it seems to keep one CPU core pretty well occupied (~17-25% utilization) the issue goes away after a reboot, simply disconnecting the KVM session does not cause the utilization to go down significantly (it may not hit the 25% max anymore, but generally stays above 15%).
It's possible this is starting after a period of idle time when the remote machine has turned off the screen or entered an early sleep mode - although I haven't been able to confirm this as the cause. The issue has persisted through a full re-install of Windows 10 on the client machine after I upgraded the boot drive.
Is there any additional logging or diagnostics I can enable in Multiplicity to try to collect more info on what exactly the client might be doing?
Both machines are running Windows 10 Pro 1803 with all the latest OS updates and the latest (I believe) Multiplicity v3.44 Build 00090 (primary machine is v3.44 KVM Pro Build 00090).
Thanks for any assistance!