Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Very High Energy Impact on Mac

Using Sourcetree v4 on a 2019 MacBook Pro 15in. If left open in the background, SourceTree is almost always at the top of the MacOS Activity Monitor for Energy usage. Average Energy Impact is listed at 109.  Compared to the next highest being Firefox at 25.6. It's also at the top of CPU, and Disk usage, even when in the background and not in active use.

If I don't remember to completely quit SourceTree when I disconnect from power, it will most assuredly drain my battery.

Screen Shot 2020-02-06 at 9.34.40 AM.png

8 answers

+1 

Joel, did you find any solution? 

+1 This is pretty ridiculous. Please fix it. I don't want to have to switch to the github client

+1 i basically can't keep it open if i'm not plugged into power.

I've found that disabling the "Check default remotes for updates..." seems to help with this.

Untitled.png

Unfortunately not working for me.

Screenshot 2021-01-19 at 13.37.58.png

+1. Having this issue on macbook pro 13" - macOS Catalina. Any updates on the topic? 

+1. I'm also facing this on 2019 MBP 16" with BigSur.

@Joel Hess did you find any solution?

I get this too

same thing here. app restart always helps.. but after some time it starts high CPU usage again

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events