Closing this ticket as this has been improved and no seen in the latest version of SourceTree.

Updated to v4.1.9 for ~2 hours.  So far %CPU is staying low.

Hi All,

Can you please update to the latest version and let us know if this issue has been resolved?

Hi everyone, 

Thanks for your feedback and apologies for any inconvenience caused by this issue.

Both this and M1 chipset support (https://jira.atlassian.com/browse/SRCTREE-7446) will be our priorities moving forward in Sourcetree for Mac.

We'll keep you updated on the progress of this issue.

Regards,

Raul

Crikes, what is it with the Atlassian Revolving Door.

All the people who work on Sourcetree seem to become (Inactive)

I posted my situation to SRCTREE-5388.

Nope, the fix is not working. I have Mac with 3,8 GHz 8-Core Intel Core i7 here, and if sourcetree with pipeline markers is in the background, it leads to lagging of the whole Mac user interface. Thats crazy.

What the heck are you sending to the windows server for repaint if sourcetree should idle? How are you even possible to generate around 50% CPU for windowserver (minus 10% for activity monitor) + 30% CPU for sourcetree doing nothing?

If I close sourcetree the window server goes down to single digit % CPU as seen in the second screenshot.

Sourcetree Version: 4.1.3 (239)

Hi Alan,

i directly downloaded the new version and it work a bit on mac Big Sur 11.4. It's not at 100%+, but idles at 20% cpu usage.

Can you fix the last 20% too?

Thanks

Hi Everyone,

Thanks for your patience.

CPU % boosting issue when we have Bitbucket pipeline enabled in Sourcetree have been fixed in the latest version. You can download it directly from here: Sourcetree v4.1.1

We are continuing to work on with the CPU issue for the larger repos. We hope we can come out with a fix soon.

Any sign of a fix on this - it's a disaster, makes SourceTree unusable.

Hi Everyone,
I'm the Engineering Manager for Sourcetree in Atlassian. I understand that this has been a pain point for all of you for a long period of time. There have been certain changes in the Sourcetree structure in the past. As of now, we have released the much-requested notarization feature in Beta. Our next target is to address this bug. While I cannot assure you of an exact date, our current set target is 3 months. I will do my best (along with my team) to provide periodic updates here. I appreciate the patience you have shown so far and request to provide us some more time to get this done.

We'll see, they still haven't assigned this ticket and I've been pestering them about it for three years.

Thanks Johan, and thanks to the SourceTree team for revisiting this issue. 

Update! I got an answer and SourceTree team will solve this issue. They will solve this and the time frame is 3 months (lol wtf?) but better later than never I guess. Someone will also post an update here this week. 

I got someones attention at Bitbucket team about this issue now. Don't know what kind of action they will take but they are aware of the problem and asked me for how to reproduce the bug. About reproduce, I guess its the same for everyone? Just use any version of SourceTree and MacOS with Bitbucket Cloud + repo with pipelines and you will get the bug soon or later after some commits right?

Ooh.  Well spotted, @modestfake !  That reduces the CPU load from 100% to about 25% for me.   Still too high, but much better! 

Seems like it's already possible to disable build statuses from View –> Hide Build Status

Here's a screenshot https://monosnap.com/file/uDjIwDAVqKQ2AAoKWti0dXiO2eSPN6

And the annoying thing is that the fix would be so quick and easy: just add an option to disable the pipelines functionality.  If I had access to the source code I could do it in half an hour

But, though I managed to work with an elderly version for quite a long time, I have now, alas, abandoned SourceTree and moved entirely to Fork.

Fun fact: This bug is over three years old and has been around through four MacOS versions. 

I'm out too. It's unreal that a company such as Atlassian can leave their users hanging like this. I'm canceling all Atlassian services for my company and moving on. We've already migrated our repos and data elsewhere. I've been following this bug for years and have struggled to use Sourcetree with their own ecosystem. I've had it. Good luck, everybody.

In a fit of pique, I finally decided to delete all my Bitbucket repositories and move to a competing provider. I explicitly said that a primary reason was the fact that this specific showstopping bug has been around for years. I'm now departing the entire Atlassian ecosystem, and wish everyone the best of luck in getting this resolved

I first commented on this bug report nearly 2 years ago. Today I've switched to using GitKraken, and am unfollowing this issue. No update from Atlassian at all on this.

I've been following this issue for years across 3 different macs, and there is not a solution that has worked for me other than disabling Bitbucket Pipelines. I've had to do that every time. I use a different CI/CD service solely because of this issue.

I face this issue and am unable to use Sourcetree efficiently. Everytime I open it, the CPU uses the whole capacity and the fan runs at the peaks.

Please provide a fix for this issue! There are so many complaints, you are constantly losing users!

We too have seen the issue after adding pipelines to our process. Atlassian, I see you as a company that really champion UX in areas of your product. As a technical product manager I look up to you in the way that you make your products.

However, I am so bitterly disappointed by the fact that this high priority issue has been around for so long. I now find Sourcetree unusable. As soon as I start it I go straight up to 95% CPU utilisation. From a customer point of view, we've just upgraded and starting paying you more money and in return, we now can't use one of your products. The only upside is that I have become far better with the git CLI...

Please fix this.

I still use sourcetree on mac without issues after disabling Bitbucket Pipelines. The issue seems to be related to that. I leave Sourcetree open all day with no issue.

I have this on version 4.0.2 on OS X 10.15.7, where securityd and trustd CPU usage goes to top and fans work as hard as possible (huge sound) - and therefore, SourceTree is completely unusable.
I was directed here, where the bug has been reported apparently almost 3 years ago -> I guess the only conclusion is that this will not be fixed. Time to look for alternatives.

Yes, this is a really good example of when open source would win. Something this annoying would have been fixed in a couple of days rather then being unfixed after years...

This is literally the single worst problem in the entire Atlassian ecosystem. Everyone hates it. How has this bug survived 2 major releases?

This is the bug that caused me to leave the entire Atlassian ecosystem forever. The reason to use Atlassian is not because any one tool is better than other tools out there - it's because it's supposed to be a suite of tools that work well together. The fact that a $50 billion dollar company can't fix an app breaking bug after years tells me that the folks at Atlassian have lost sight of the needs of their users and customers. It was nice while it lasted.

We are happily using ClickUp, GitLab and Fork now. If you are looking for tools that are maintained by responsive and customer-focused teams, check these out!

Looks like it's been moved to 'Long Term Backlog', the definition of which is:
'A fix for this issue is required, but planned for farther in the future. This is because it’s not as severe or pervasive as other issues.'

Really curious as to which issue is more severe or pervasive than this...

We are in the process of switching our team to https://git-fork.com/ - really impressed so far, would highly recommend.

I switched to GitKraken thanks to this bug. And I'm very happy with it. 

Thanks SourceTree

I had some contact with GitKraken team and I noticed them about this problem. They have started on the feature that supports Bitbucket pipelines so its coming soon. I dont like GitKraken in the same ways as SourceTree but after they added that feature at least your computer will not be in pure pain.

I forcefully used SourceTree before and after some time by battery in my Mac turned very bad and have I Service recommended" warning. Can't tell for sure its because SourceTree but its the single app that has been hitting my computer very hard. 

Its fucking INSANE! Probably a one day fix if someone would looking at this....

For me, I am not using Bitbucket Pipelines, I am using a company internal pipelines which will trigger build in Jenkins to run the build, not sure if this issue is with Bitbucket Pipelines specifically. 

Yeah, it's a choice!

a) use Bitbucket Pipelines => you cannot use SourceTree

b) don't use Pipelines => you can use SourceTree

Sorry, you can't have them both!  

see: https://jira.atlassian.com/browse/SRCTREE-7066

I decide to stop using sourcetree today, sourcetree has great features, I love it, but I can't sit with a MacBook 12-18 hours per day with loud noise from the fan. Sad.

Keep me posted with this bug fix.

Or if the original reporter is still around, update the affected versions on this ticket

I stopped using SourceTree because of this issue. It made the app unusable. I've been complaining about this bug since 2018. Atlassian recently replied to me on Twitter about this asking if this bug was still present in 4.0.1 but I haven't bothered to re-download the app to check. If this is still going on it might be worth opening a ticket ticket against the 4.x version and linking this ticket to the new one as reference.

I give up... Me and my team has moved to Git Kraken. I really dont understand this and its quite frustrating that we pay quite a lot every month for Atlassian services and they cannot look at this bug. Why even bother to update other stuff in SourceTree when not everyone can even use it.... thats beyond sanity! I also got "Service recommended" notice on my battery thanks to this shitty app. 

Good luck everyone!

This bug should be higher than "Minor" classification. I've had it derail an entire day of development when I didn't notice Sourcetree was using 100% of my MacBook CPU, and it drained my battery extremely quickly.

Thanks for the link, Quentin – I've sent a tweet to the official sourcetree Twitter account myself.

Ha!  Thank you Anthony!  Downgrading to 2.5.3 is indeed a good way to fix the problem for now!  I may actually be able to use SourceTree again!  The download archives are here:

https://www.sourcetreeapp.com/download-archives

I've sent a FB message to product owner Eric Henry some weeks ago and now I tweeted @askatlassian on twitter. I think we need to get attention some where but not here. This is insane because this kind of bug should be top priority since it makes the app totally useless. I cant even open it on my laptop because it will drain the life out my battery in 20 minutes. Im using 4.0.1.

Atlassian stopped caring about desktop users a while back: if you're not cloudy you don't exist. They've probably disbanded the SourceTree team by now.

Downgrading to version 2.5.3 is a workaround to this problem (which still exists for 2.5 years...)

macOS 10.15, freshly-opened SourceTree v4.0.1 (234); in other words, the latest stable environment and app.

110% CPU usage and climbing, no matter which Workspace I view. At the time of the screenshot, I was just on the empty Search Workspace. Repository Browser window closed.

I'm going to have to switch to another tool; SourceTree is making my fan spin up.

Running into this today (May 27 2020). Consuming a ton of CPU on a 6-core MBP 2019. All because of the build status icon spinning uncontrollably.

Yes, I'd be very happy with a simple option to disable Bitbucket Pipeline support if it stopped this bug.   Pipeline support is a nice idea, but it may as well be removed completely if people can't use it for this reason!

I still use SourceTree by preference on the projects which don't use Pipelines, but the vast majority of my work needs to be done with Fork now, which is fine, but not quite as good, in my opinion.

Perhaps those of us using Bitbucket Pipelines could start petitioning for Bitbucket Pipeline support to be removed!

Thanks to those that have mentioned Fork as an alternative to SourceTree, works well, really impressed. Hoping to switch our team over soon.

@Atlassian - This is still very much an issue. It would be great to get an update, at a minimum to update the details on this ticket and acknowledge the severity - it's still affecting the latest version and it is the very definition of a blocking defect. I know it's a free product and it can't be an easy fix or you'd have done it by now. However, in my opinion there is little point releasing any other changes or fixes whilst this issue still exists.

Still happening on Mac

We will celebrate 2 years anniversary for this ticket soon

Let's get a party!

Good idea - though I might have used less inflammatory language for a free product  

Have voted.

If you are still watching this issue, please cast your vote here: https://jira.atlassian.com/browse/SRCTREE-7066

if they can't fix this issue they could at least give us an option checkbox to disable their problematic bitbuckt-pipeline feature to save our toasted CPU.

Just started using pipelines and running into this issue now too, definitely disappointing to see how long this has been sitting out here with no movement.

I (and our team) can confirm @Haoyu's comment: remove `bitbucket-pipelines.yml` will solve the CPU issue.

We actually stopped using Bitbucket pipeline altogether 

They should have known the issue is with their integration with Bitbucket pipeline, if you remove this file LOCALLY from all of your open repos

bitbucket-pipelines.yml

and restart SourceTree the CPU will be back to normal, but don't push this changes to your repo because it will remove pipeline support for real.

So, the easiest workaround Altlassian, you could just give us an option, a checkbox to disable your not-so-useful and counterproductive Bitbucket pipeline client side support (for Mac), please, how hard is that? Need help?

Unbelievable!

This bug is set to low but really it is critical.

How can we get Atlassians attention to this? Clearly they don't know about the issue.

Updated to SourceTree 4 today, same problem. The CPU is 98% all the time... this should be the highest priority for SourceTree team? How can this issue been around this long???

@atlassian you can mark this problem as resolved. Installing Fork fixes it 🤬

This also caused me to switch to Fork, which works well, though I don't like its UI quite as much as SourceTree.  

I think I'd still switch back if they ever fixed this issue.

I am with @Aleksandar on this. I used the git client Tower, but dropped it after they switched to the subscription model. I'm not a hardcore Git user, so the price was to high for what I use Git. I switched to Sourcetree (not a fan of its GUI) and had that nasty high CPU usage problem. After reading about https://git-fork.com/ in the comments I tried it out, and I'm very happy with it so far; for me the »Fork« Git client seems to be very intuitive to use - I like it a lot.

And its free – for now. I would not mind to pay for it!

I started using fork. Best thing I ever did.

Atlassian don't give a fuck about this major issue. I already raised it multiple times and they close it as solved. Fortunately me and my colleagues find the solution in comments above and it's **[Fork|https://git-fork.com/] It's almost the same UX and take us just few days to get comfortable working with it. Now after almost half a year of using it I could say it's even better than SourceTree

Still a problem for me with Sourcetree 4.0 on Mac. I think it's fair to say this clearly isn't a priority for Atlassian 

Same here, my laptop fan is always spinning, assumed it was having multiple IDE open normally, now after discussing with co-workers i've notice last few days SourceTree is the bad guy here with very high CPU even when not in use. 

My repositories ever contain neither pipelines nor Bitbucket remotes, however it freezes.

Brand new install (v3.2.1 225) on brand new MacBook Pro (2019). Staying around 100% CPU.

Likewise seeing this issue, Version 3.2.1 (255). Frequently sits around 100% on Activity Monitor, then settles down after some time to 0-4%. macOS 10.14.6 Beta (18G48f), MacBook Pro 15-inch, Mid 2014. I did recently add bitbucket pipelines to two projects, though I see the performance issue even when those repo windows aren't open. Unsure if the performance issues only started after adding the pipelines, could be though.

I can confirm that the bitbucket-pipelines CPU load issue is still a problem in 3.2.1.

The problem certainly still exists. The problem goes away by renaming the

bitbucket-pipelines.yml

file to something else, then restarting the application.

With Pipelines enabled and if that file exists the application is basically impossible to use, and slows the rest of the machine down to a crawl.

This ticket has been opened more than a year ago.

Could we hope some news or, better, a fix ?

I just upgraded to 3.2 and the problem still exists.

Yes, I've loved SourceTree for a long time, and greatly appreciate what it's given me (for free) over many years, but this has, sadly, forced me to look for alternatives.

I'll come back if it's fixed, though!

Please add someone affected version 3.2. 

Sourcetree is absolutely unusable currently. Switching to Fork until this is fixed.

Still an issue in V 3.2! Very High CPU around 100%. Independent from which options I activate/deactivate in Settings. Even in idle mode (doing nothing - no open repository, just the repo browser eats 100% CPU). Running MacBook Pro (15-inch, 2017)

The bug still exists and the workaround is to use cputrottle: http://www.willnolan.com/cputhrottle/cputhrottle.html

I didn't see any reference to this in th recent 3.2 release so I assume you're still doing the heavy lifting, right?

Thanks for the update, Brian. Very much looking forward to the update whenever it's ready.

Okay I can confirm that hiding build status does not work, and I have the same issue as Suresh Joshi. As soon as the pipeline starts, Sourcetree is stuck on 50% CPU now (instead of 100).

Going to give fork a try.

My team has moved to using Fork and for the most part have been happier for it, does the lions share of what sourcetree does, but it is snappier and no CPU issues.

I just tried that on your suggestion, and we're down to jumping between 20-50% CPU. So, while an improvement.... Not REALLY an improvement that would allow me to keep SourceTree open.

Hard to use a Git tool that uses more CPU than my compilers and IDEs do.

Also, woke up to an amusing slap in the face, when I got the email from Atlassian about the VS Code plugin that lets you view your Pipelines status from within VS Code... No chance I'd install that right now.

Hiding the build status, then restarting source tree seems to have worked for me [Version 3.1.2 (216)]

Is there a workaround to disable Pipeline build status? I enabled Pipelines today in 3 of my 50 projects, and I can no longer leave SourceTree open as it runs at 100% CPU

Hiding the build status from View, or even just closing all open windows, doesn't do anything. My best idea right now is to disable integration with Bitbucket entirely.

Improvements for Pipelines performance are on our list for an upcoming update. The biggest source of improving it requires some heavy lifting to replace how the History view is rendered (NSCell versus NSTableCellViews for the curious) We're sorry for the performance issues in the meantime.

Brian Ganninger
Principal Developer, Sourcetree

I am glad I found this thread, it was 100% pipelines for our team. We were using Sourcetree for years with no issues and just recently (last month) started using pipelines on one of our repositories, after that sourcetree started using 100% CPU on all of our macbooks (We noticed because we don't normally hear the laptop fans going for everyone in the office).

We removed the bookmark to the pipeline project, and source tree is back to normal.

If it happens again, you can solve it with http://www.willnolan.com/cputhrottle/cputhrottle.html

The new beta is performing better for me, but in the process of upgrading, my build status is no longer visible, whereas I believe that previously the visibility of build status did not matter (only pipelines integration did). So, this may be progress.

I inadvertently was running an old 2.6.3 version.

Same for me, I'm getting the same high CPU with the Beta. For reference to replicate this:

1. Open a repo using the Sourcetree Beta version, one with pipelines enabled and build status visible.
2. When this window is visible or in the background, CPU runs at 90%+ continuously.
3. Only goes away when I close Sourcetree completely.

I can also confirm that the hight CPU consumption still is there with the beta version. 

Thanks for looking into this! On my machine there is no difference in CPU consumption, the beta is on the same level as the release version, so unfortunately it doesn't address all issues leading to high cpu usage.

If you need sample logs or screenshots please let me know!

We do have a possible fix to this issue which is currently in Beta Version 3.1.2. You can test the Beta Version on this link.

Link : https://bitbucket.org/atlassianlabs/sourcetree-betas/downloads/OSX_Beta_Latest.zip

This is not an official release yet as it's still in beta version.

None that I have seen. I am slowly learning how to use Rider's git integration...

+1 this is a terrible bug, any response at all from Atlassian?

My biggest gripe has to be with the complete lack of communication from Atlassian over this issue. Elsewhere I've found Atlassian to be helpful and engaged (upcoming fix for Sourcetree re. not selecting all files in a commit) so the tumbleweed here is disturbing. SourceTree is an excellent program but the longer this issue is left to fester the more people will look for alternatives, if they can: I'm use Mercurial so I don't so much choice but also don't find the problem that bad.

I switched to GitHub Desktop + terminal, month ago(

Great thread and incredible bug handling by a major company. Our whole team is affected by this issue for more than a year. Fortunately I am slowly getting accustomed to quitting the app after working with it.

I am seeing this on a brand new macbook pro:

Is there any word on recognizing this as an issue and fixing it? I've been through several releases hoping each time that the issue is fixed. 

The priority is low and unassigned, is there something missing here that would make this a real issue for Atlassian? My battery can't handle this kind of power suck constantly.

Please fix this. The only reason we pay for Atlassian products is because they are supposedly nicely integrated together. This is preventing us from using Sourcetree and is a big motivator to migrate. Atlassian is a 25 billion dollar company and one of its core products has not worked on Mac for over a year. 

@fbucek1013785738, thanks for the heads up about Fork, giving that a try. 

I can't have a git tool eating 100% of my cpu, running a dev node server for build/host is bad enough. 

SourceTree for Mac bugs ordered by votes
https://jira.atlassian.com/browse/SRCTREE-5306?jql=project%20%3D%20SRCTREE%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Needs%20Verification%22%2C%20Verified)%20ORDER%20BY%20votes%20DESC

This bug has the most votes. One year and no attention and low priority.

Atlassian issue:

Problem of Atlassian is that it has so many features and services that its own people does not know how to work with them. 

I have recently switch to Fork as desktop git application as suggested here in discussion and I will in future also switch all my project from Jira to GitLab. All new project uses GitLab only. Because sometime less is more. Atlassian has complex tools, but it seems that not even Atlassian coders use them. I notice new features but also changing UI with chagning layout and animations but without any advantage. Bitbucket and Jira works together but for me connection is too chaotic. But maybe I am using it wrong way, I do not know.