SourceTree 4.0.1 super high CPU usage on MacOS

[Gilfoyle]

I've seen this problem reported since SourceTree 2.7 and I can't believe it's still not fixed in 2+ years, therefore I hope I'm doing something wrong.

Bug Description:

SourceTree consumes all of MacBook's CPU while doing exactly nothing.

Repro Steps:

1) Open SourceTree

2) Open a Repository (BigBucket connected - I don't know if this matters?)

3) Do exactly nothing

4) Watch the CPU consumption to grow and grow above >200% - untilt the MacBook's fan goes crazy

[Justin Fiedler]

I had been dealing with this issue for way too long and and finally found a solution.

1. Close SourceTree

2. Install Github Desktop - https://desktop.github.com/

3. Never use SourceTree again

It's unfortunate that this issue hasn't fixed by Atlassian. SourceTree is a great app but this is a deal breaker. I can't continue living in fear that my idle Git client is going to start using 120%+ cpu every time I have it open (aka always).

[jfjcn]

I was having the same issue forever.  I found this:

https://apple.stackexchange.com/questions/110198/securityd-using-100-cpu-and-polluting-system-log

Read down to the part about Keychain.  I had a bad account in my keychain, and it was causing these exact CPU issues.  Removed the bad entries in Keychain, and now everything is just fine.

[Gilfoyle]

Thank you @jfjcn I appreciate your answer. I resigned on using SourceTree about a week ago (I'll describe my reasons below) but I still have my old account, I will try your tip just for completeness sake.

[Maddin]

I have the same issue with Version 4.0.2 of SourceTree. But the hint with removing entries in Keychain doesn't work for me.

[arifjusoh]

Having the same issue (version 4.0.2).

Did remove all entries related to source tree. But it does not work for me. 😅

[Rafael]

It worked for me! It seems to be related to the issue because my cpu got to 95% after I entered a wrong credential for a repo.

[Gilfoyle]

Ok folks, I solved it in an unusual way, not suitable for everyone but wanted to share.

I got super-frustrated about Atlassian because there is no way to contact their customer support and Atlassian stuff is absolutely unresponsive in this forum.

A week ago I stopped using SourceTree and shifted to Visual Studio code with Git History plugin. It works excellent for me. Not only have I solved my CPU problem but I also got some more features that I've been waiting for for long-long time, such as:

• Viewing Git history of one single file
• Viewing Git history of all files in a specific folder

Thanks to the community driven nature of VSCode plugins it's much more actively developed than the abandoned SourceTree.

I think it is a no way back for me.

[BenStaveleyTaylor]

I'm stuck in my ways and I don't want to learn a new Git client right now :-). It seems that a workaround is to hide (Cmd-H) SourceTree, and the CPU usage quickly drops to 0% while hidden. Not ideal, but it soon becomes muscle memory when you stop actively looking at the SourceTree window.