Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sudden jump in SourceTree CPU usage on Mac with BitBucket Pipelines?

Running MacOS 10.14.5, SourceTree 3.2 (224)

I just started using BitBucket pipelines. SourceTree started popping up build success/failure messages, and my Mac's fan started to spin up dramatically. I noticed SourceTree was suddenly 'Using Significant Energy.'

I've been using SourceTree without issue for years, and this suddenly started, literally the moment I kicked off my first Pipelines build. Very weird. Disabling SourceTree notifications doesn't help, nor does killing and restarting SourceTree.

After some testing, it appears that while a BitBucket Pipeline is executing, Sourcetree starts using a ton of CPU time. As soon as the build is done, it drops back down to load CPU usage. Pretty weird.

3 answers

I give up using BitBucket Pipeline because of this issue.

There are no better options for Git client, but there are many options for CI.

If this issue would be fixed, I'm willing to come back to BitBucket Pipeline!

Hi Brian,

I'm facing the same issue with SourceTree where the CPU usage suddenly spikes up while switching branches.  Looks like this has been an issue for many since 2 years.  Is there a fix already, or can it be expected soon? Please update.


0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 29, 2019

Hi @Jason Machacek,

We are aware of some architectural limitations around the Pipelines feature that cause the CPU spike you noticed. There are plans to address this in a future update. Thank you for your patience and feedback!

Brian Ganninger
Principal Developer, Sourcetree

Thanks for the update! I'm a big fan of Sourcetree. Good to know a fix is in the works.

So @bgannin... How's the update coming along?
Been a while and the issue remains.

Using 4.0.2-build (236) and have to close the app between commits so that the battery won't get more worn down. 

March 2021. I'm using 4.1.0 on a Bitbucket project that happens to have Pipelines, not that I care about that stuff when doing local development. Sourcetree is kind of unusable for me due to high CPU. Ironically, I guess I can only use Sourcetree on GitHub projects...

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events