nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SourceTree 3.1.2 100% CPU usage on Mac

emil.lewandowski

This has been posted a few times times, since Dec 2017, and the first Question (link) has been closed and I don't know why, so I'm attempting to ask this again, to see if there's an update.

I am getting constant 100% CPU usage when running Sourcetree 3.1.2 on Mac OS Mojave 10.14.4

Any ideas as to why?

Thanks!

Here's a photo of the sample of my Sourcetree process. It seems to be increasing the load around the '_drawContentAtRow' instruction... Not sure.

Screenshot 2019-05-03 at 11.54.47.png

Accepted answers

sam.arbid

Vote here if you come after 2020 and still have the same issue.
same issue for YEARS!
Unbelievable Atlassian. 👎🏼

All comments

bgannin

Hi @emil.lewandowski,

That particular discussion devolved over time and was closed officially with this comment.

We're tracking the performance issue (as shown) in relation to the build status column [SRCTREE-5306]. Fixing that requires a bit of rearchitecting of the history view and is on our roadmap for a future update but I can't provide a specific timeline at the moment.

We apologize for the hassle and are keen to address it comprehensively.

Brian Ganninger
Principal Developer, Sourcetree

emil.lewandowski

Thanks for the update Brian, and thanks, of course, for the continued development of SourceTree, and for making it free for the public.

Looking forward to more news, in future.

Andreas Ek

The life hack to this is to use cputrottle. http://www.willnolan.com/cputhrottle/cputhrottle.html

nutmix

I have the same issue. SourceTree uses 40-100% of CPU on the most expensive 2018 macbook pro model when source tree is idle. It has been like this since I started using sourcetree about a year ago. The workaround for me is to open source tree, open my project, commit/push etc, then immediately quit source tree completely. If i forget to quit ST, then I soon know it because the fans start blowing. A quick trip to activity monitor and its source tree again.

You certainly cant use souretree if you are on battery.

Niklas Kolster

current beta release still has this issue

Kuba Domaszewicz

Can confirm

Bowen Fan

Ever since I encountered this problem, I've been resorting to using Git command line out of frustration. Now after months of practice, I've become a Pro in Git commands. Therefore I would like to thank SourceTree for implementing this 100% CPU feature which enabled me to upskill in my Git proficiency. Keep up the great work guys!

Andreas Ek

Atlassian is so unbelievable uninterested to solve this issue affecting their users.

Are there som missing bits here? Don't they understand the issue?

Charlie Jonas

Same here.

LouAdrien

same same for years. I want to stay with sourcetree but eventually gonna have to move on

Matthew D

They've abandoned the project. This app is dead.

jacklin10

This is / was still a problem for me on MacOs even on version 4.0.1. I recently changed a few things that seem to have helped a bit that I'll share with the hope it helps someone else.

First, I had tons of repositories linked in SourceTree. I removed the bookmarks for all the repo's I am unlikely to touch any time soon. I have 12 in there now down from about 30.

Next I removed any setting that does any syncing or or auto refreshing.

In preferences "general" I unchecked:

"Refresh automatically when files change"
"Check default remotes for updates every [10] minutes"
"Load Gravatars for authors"

I did this yesterday, and I've been monitoring it today.
I haven't seen the usually spikes to 100+% cpu usage. I say spike, which implies a brief time, but it sometimes it stays pegged over 100 until I close the app.

After the changes I'm seeing spikes between 14-25% cpu while I'm using the app.

You'll need to cmd+r more often to manually refresh, but i'll take that over the cpu problem until they can get it fixed.

Steve Pascoe

My guess is this is something to do with excessively checking Pipelines. The spinner is rotating out of control. Probably something small to do with the animation. With these things its always something annoyingly small thats the cause. But yes i have been experiencing this CPU issue for a number of years now, might be time to consider an alternative.

Ivan Parfenchuk

Also seeing high CPU usage on macOS 10.15.4 (19E287), Sourcetree 4.0.1 (234). Almost always 100%. Drains MBP battery too fast.

Turning off automatic refresh on file change did not help.

sam.arbid

Vote here if you come after 2020 and still have the same issue.
same issue for YEARS!
Unbelievable Atlassian. 👎🏼

nebrekab

I switched to GitKraken as I gave up hope...

Steve Pascoe

My opinion is its almost certainly got to do with repos that have Pipelines builds associated with them. That or bitbucket repos in general.

I have two windows open now, one repo to AWS CodeCommit, the other to github and CPU is fine. If i open a bitbucket repo (that happens to be attached to Pipelines) i hear my laptop getting ready to take flight.

Ralph Callaway

happening today with v3.1.2 (216) on mac os 10.14.6

checked console and didn't see anything in the logs per https://confluence.atlassian.com/sourcetreekb/sourcetree-logfile-location-675384748.html

the repo has a pipeline, haven't adjusted any options

checked open ports and files and ran a sample, nothing i could get anything from although i have know clue what i might be looking for

fshamim

really unfortunate.

xuanxian

If the repo enable the pipe, The cpu will more 100%, I download v2.6.3 from to https://sourcetreeapp.com/download-archives , It do not support pipe, so can work well.

Hope the information can help.

Dave Hale_n0w9ve

I've actually grown to love the soothing white noise of my CPU fan coming on. Sure it will drain some of the useful life out of my computer due to wear and tear, but that's nothing compared to the blissful peacefulness I get from the calming whir of the CPU fan. So zen! Please don't fix it!

wadesign

I'm running version 4.1.0, on MacOS Catalina.

And this bug is driving me crazy. Is there any idea if, and when this issue will be resolved?

Ralph Callaway

it goes away as soon as you stop using source tree, i've switched to vs code's internal git tooling (along with the gitgraph and gitlens plugins)

the comment above this has links to older versions that don't have this bug (and don't support pipelines, which is fine since that seems to be the cause of the bug)

Jeremy Tredway

I can confirm that after removing a deprecated pipeline.yml file, the CPU usage went from 90%+ down to 0% when idle.

Jeremy Tredway

I can confirm that after removing a deprecated pipeline.yml file, the CPU usage went from 90%+ down to 0% when idle.

wadesign

Hi Jeremy, hope this will work. where to find this YML file?

Andreas Ek

Perhaps in your repo 😂

Hasanta Sumudupriya_1yfis4

Removing some of the bookmarked repositories helped me too. Thank you for your solution.

ture.friese

Upgrading to version 4.0.2 helped for my part. The high CPU usage is gone.

Dirk Flachbart

Just upgraded from 4.0.1 to 4.0.2, unfortunately didn't solve anything for me, CPU still at 100%

Tristan Richard_ta2vb2

This seems to be a MacOS Bug. I am having the same issue with Git Tower

afenn

This was supposedly fixed in 4.1.1

TBD if it fixes the battery drain issues discussed here:

https://community.atlassian.com/t5/Sourcetree-questions/Sourcetree-3-1-2-is-murdering-my-Macbook-battery/qaq-p/1056533

Sourcetree 4.1.1 - Minor Release [16 April 2021]

Notes

Requires macOS 10.14 or later

Bug Fixes

Updated embedded git version to 2.31.0 to address security issue
SourceTree high CPU usage for Pipeline enabled repos
Repo Window Toolbar buttons changed it's position after upgrade to Big Sur
Some of checkboxes in Pull / Merge / Ignore popup are clipped on latest Big Sur

From the release notes:

https://product-downloads.atlassian.com/software/sourcetree/ReleaseNotes/Sourcetree_4.1.2.html#version-4.1.2

Arda_8ny9t4

In my case, the culprit ended up being the file diff pane in History mode. A specific set of changes to a text file has been causing SourceTree's CPU usage to skyrocket and stay that way even though everything seems to be working fine otherwise (the diff pane displays the changes correctly and SourceTree is still fully responsive). Switching to other apps doesn't make a difference; CPU usage remains very high. However, selecting other History entries or changing the diff pane's "lines of context" setting to a different value fixes the issue immediately. The CPU usage is consistently high only when the specific history entry is selected.

I've tried creating a clean repo with a single file and just 2 commits that replicate the same textual changes, and got the exact same high CPU use issue. So this is not about anything else in my original repo, but something about the type/pattern of changes that are displayed in the diff pane. The only thing that stands out about the specific textual changes is that one of the lines before the change is rather long (290 characters).

If I'm not mistaken, simply changing the pane's size fixed the issue a couple of times too, but not consistently.

This is all on a Mac with an Intel processor. I've tried viewing the same history entry on a Mac with Apple's M1 chip and also on a Windows computer, but didn't get the same high CPU usage. But obviously there are many differences between the computers, including their screen sizes.

In short, if you're experiencing high CPU usage, try viewing different history entries and/or changing the diff pane's "lines of context" setting and see if that helps.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

sourcetree

performance

mac