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.

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.

I have given up and moved to another application that actually works.

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