I recently updated to Sourcetree 2.7 (144) and I've noticed very high CPU load when operating on a Bitbucket HTTPS git repo - just typical commits and pushes.
It first came to my attention when I noticed the fan on my Mac OS High Sierra 10.13.2 machine was blasting after using Sourcetree for just a while. The CPU load in Activity Monitor showed >150%.
Even when it was idle, the CPU load would drift between 60-150%.
The machine specs are MacBook Pro, 2.8 GHz Core i7, 16 GB RAM, 185GB of free disk space on a 1TB SSD.
I've loved SourceTree for a long time, but this issue provided an opportunity to check out the upcoming Tower 3, and I have to be honest, I'm not sure I'll come back to SourceTree even if Atlassian ever decides to take this seriously and fix it. The new Tower is a pure joy to use. SourceTree could stand to take some cues.
I've identified a [the?] primary source of spins for our next major update, which just started internal alphas. The overall issue of performance is definitely not being ignored; it's challenging for our small team to balance responding to everyone and providing details while debugging reports and doing feature development. We appreciate your patience and enthusiasm and are working hard to this resolve pain point.
Senior Mac Developer, Sourcetree
Thanks, Brian. It seems to me that performance should be your primary concern. I'm now trialing Tower because of this - which is a shame because I think the SourceTree UI is great.
If you could keep us up to date with progress then I think you'll keep us all.
@bgannin I thought I would give the 3.0 Beta a try (196) and I see sustained high cpu use still, but it is less than it used to be. It was 90% now it is 35%, but I also got a significantly more powerful MacBook pro, so I don't know if the software or hardware is to blame for the improvement. At any rate, sourcetree continues to be the main battery drain on my laptop.
Do you have any more updates you can provide?
@bganninThis is insane. Your product has been unusable on Mac for almost a year now. Why even bother allowing people to download it? Why pretend that it works?
How many newbie users are running your software and thinking they need to buy a new computer? It's just unethical at this point. Your software is critically flawed on Mac - you should at least tell Mac users it's broken before you allow them to use it.
This appears to still be the case on 2.7 build 152, High Sierra. Unlike the initial poster, I see the symptom with SSH repositories present, so it is not specific to HTTPS. It wastes approximately 100% of one CPU all the time while running, idle. Ample disk, ample RAM, a couple of versions back there is no such problem, so I don't think there is anything about the machine causing this problem, but rather only a defect in the current source tree. This is... not ideal.
Unfortunately the only workaround I've found for this is to use a different Git tool when operating on battery.
I found the solution, after waiting on this fix for more than three months!
I didnt want to have to ask my employer for a new paid software, since this has been a really bad example of when you just dont get listened too.
We found another alternative, its called git-fork, and is free...
Check it out on: https://git-fork.com/
what is a joke is how long a big software company like Atlassian is making us wait for fix to solve a fundamental issue making their software unusable on Mac OS. Sourcetree might be free but i for one use many Atlassian products that are not free in my workplace and this issue is damaging their reputation with the developer community. Many of use are looking for alternatives or just giving up and using Git integrations inside the IDEs
The SourceTree 3.0 Beta has a lower energy impact than Fork on my main repo (only ~7000 files, granted), over the last 10 days, both mainly in the background. So no need to give up on SourceTree yet.
As others have mentioned, if you have CPU issues with 2.7, reverting to 2.6.3 works fine.
Happening still on
- macOS 10.13.3 (17D47), MBP 15" Retina 2015, 2.7GHz 16G RAM
- with SourceTree 2.7.1 (159) git-embedded 2.5.1 git-lfs 2.3.4
CPU usage for SourceTree process won't go under 40%, with just 1 repo window open, git+ssh from bitbucket.org.
I tried system git (2.6) and different other repositories. Waited for 15min to "chill down", but still no less than 40% CPU. Laptop fan is blasting continuously...
I can't use the app anymore. I'll do the archive-download of an older version ...
Too bad, it was such a great app about 1 year ago, when it wasn't probably bloated with all the new fancy (useless?) features :-(