Latest Unity Hub 3.17.1 'mini' spiking Mac CPU

[phaelam]

latest update of Unity Hub causes weird spiking in CPU, Mac OS 15.7.5. prior to this update, idle computer with Hub running lay flat. now it spikes user load between 1 and 20%, where it used to sit at around 1.5%

constant, as long as Hub is open. you can see, far right, the moment I closed Hub.

[publisher_unity688]

I am having the same issue, the hub is constantly taking about between 10-20 % of the cpu

[makaka-org]

Please submit a bug report via Unity Hub Bug Reporter as well:
Unity Hub > Help > Report a Bug…

Also attach here the internal number that you will receive via Email after submitting. Only a post with such a number makes sense here on Discussions as common experience says.

@christophera_unity @toddbunity @kaylafortin

[christophera_unity]

Hi folks,

Thanks for the reports! We’re internally testing some fixes for the CPU issue in the latest release. We’re planning to have a fix released this week

Thanks for your continued patience!

[phaelam]

patience!? more over, thanks for quick response…and letting me use the engine! I was just doing due diligence when something looks odd. thank you.

[redwyre]

I’m getting this too, it’s just spamming the log with this, about every 3 seconds:

From C:\Users\redwyre\AppData\Roaming\UnityHub\logs

{"timestamp":"2026-04-17T08:31:21.054Z","level":"error","moduleName":"UVCS","pid":16228,"message":"[getUVCSWorkspaceInfo] Failed to get workspace info { projectPath: 'AAAAA', error: \"Error: Unity VCS client is not correctly configured for the current user: Client config file C:\\\\Users\\\\redwyre\\\\AppData\\\\Local\\\\plastic4\\\\client.conf not found. Please execute 'cm configure' to perform a text mode configuration or 'plastic --configure' for graphical mode. (cmSource: external-module, command: showselector)\" }"}
{"timestamp":"2026-04-17T08:31:21.054Z","level":"error","moduleName":"UVCS","pid":16228,"message":"[getUVCSWorkspaceInfo] Failed to get workspace info { projectPath: 'BBBBB', error: \"Error: Unity VCS client is not correctly configured for the current user: Client config file C:\\\\Users\\\\redwyre\\\\AppData\\\\Local\\\\plastic4\\\\client.conf not found. Please execute 'cm configure' to perform a text mode configuration or 'plastic --configure' for graphical mode. (cmSource: external-module, command: showselector)\" }"}
{"timestamp":"2026-04-17T08:31:21.055Z","level":"error","moduleName":"UVCS","pid":16228,"message":"[getUVCSWorkspaceInfo] Failed to get workspace info { projectPath: 'CCCCC', error: \"Error: Unity VCS client is not correctly configured for the current user: Client config file C:\\\\Users\\\\redwyre\\\\AppData\\\\Local\\\\plastic4\\\\client.conf not found. Please execute 'cm configure' to perform a text mode configuration or 'plastic --configure' for graphical mode. (cmSource: external-module, command: showselector)\" }"}
{"timestamp":"2026-04-17T08:31:21.058Z","level":"error","moduleName":"UVCS","pid":16228,"message":"[getUVCSWorkspaceInfo] Failed to get workspace info { projectPath: 'DDDDD', error: \"Error: Unity VCS client is not correctly configured for the current user: Client config file C:\\\\Users\\\\redwyre\\\\AppData\\\\Local\\\\plastic4\\\\client.conf not found. Please execute 'cm configure' to perform a text mode configuration or 'plastic --configure' for graphical mode. (cmSource: external-module, command: showselector)\" }"}

These project don’t have any source control (no git) so it must be trying plastic which isn’t set up. Either removing the projects from Unity Hub, or initialising an empty git repo (git init) in the projects stops the logging.

This doesn’t completely stop the cpu spiking but does reduce it considerably.

[christophera_unity]

Now Available: Unity Hub 3.17.2

Hi folks, Hub v3.17.2 is rolling out now! All the bug reports you made were invaluable in helping find the cause of the performance issue. Bug fixes & improvements Fixed an issue where users experienced high CPU usage during startup caused by excessive file watching and missing version control configurations. Fixed an issue on Linux where .deb package installation could fail on some setups when AppArmor profile loading could not complete in the kernel. Fixed an issue where the bundled Unity…

[phaelam]

Nice.

What I’ve been doing is just load project, shut Hub.
Works for now

[phaelam]

Thank you

Just checked. That did it. Thanks again.

[f03n1xDev]

I have the latest version (3.17.2) but I’m still getting massive CPU usage.

[publisher_unity688]

Still getting high cpu usage after the update

[dustin_tripp]

Same. I’m on 3.17.2 as well - it is taking over 60 seconds to even start loading a Unity 6.3 project (the loading screen doesn’t even appear)

[skaxander94]

3.7.11 and 3.7.12 are horrible. Hub is broken now.
I Installed deprecated version from here: Install a deprecated Hub version • Unity Hub • Unity Docs
Deprecated is fine.

[frank-ijsfontein]

Beta version 3.17.3 is better: down to nearly 0% CPU when not doing anything

[kaylafortin]

Hi folks - crossposting my message from another discussion topic,

We just released a patch (Hub 3.17.3), that should fix the high CPU usage that a lot of you have reported.

Our team has been working hard on a fix for this since reports started coming in. Thank you for reporting the issue and for the feedback on the latest updates. We really appreciate it all - the good and the bad Your experience matters to us and we want to get it right!

Please let us know if you’re still seeing any issues after updating.

Thanks for the patience.