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

Tip from the team: debugging Sourcetree

Supported Platforms

  • macOS
  • Windows

If you're reading this and it's not just educational… we know you're unhappy right now and apologize for that (sad) We're dedicated to improving your Sourcetree experience.

We need your valuable feedback though to help narrow down the problem and ship a fix that much faster. Here are some high level details on what we've already built into Sourcetree to aid in flipping the switch from:



Visit the Advanced preferences pane and turn on the Debug menu to make it easier to access options and logs. As noted, some changes (such as the log level) require you to restart the app for them to take effect.

Screen Shot 2018-05-10 at 2.57.29 PM.png

Once the Debug menu is enabled, you can:

  • Change several logging settings
  • Open up debug monitors and inspectors to see what's going on
  • Use the Tasks Monitor to help determine what actions are being run in response to a particular click
  • Use the Network Monitor to help determine what activity is generating traffic unexpectedly, such as populating the remote repositories list in the background

Screen Shot 2018-05-10 at 2.54.23 PM.png


It's even easier to get started finding behind the scenes activity on Windows via the Process Log under the Tools menu. When you open it, you'll see data presented like so:


 To enable logging in general for the app you'll need to edit %localappdata%\SourceTree\app-{version}\log4net.config and set the value to DEBUG. (more details) Once you've done that you'll find the output in %localappdata%\Atlassian\SourceTree\sourcetree.log

Despite the playful gifs and useful functionality we built in, it's never fun to run into a problem with tools you depend on day in and day out. We appreciate you taking the time to learn what's available to help file the most informative and actionable tickets possible.


Thank you for your help in eliminating those pesky bugs!

Note: debug data is generated only a when monitor is open and none of it is ever transmitted off your machine

Additional Reading:


Guys, I appreciate you want to fix the bugs but a lot of them are so fundamental. Like the commit button sometimes works, sometimes doesn't. Have to click it twice, three times. You have a rock solid Git layer underneath a GUI. All that is needed is to get the presentation right. Rather than getting your users to do testing, maybe look at what more your test department and QA can do. 

Like Kevin likes this

I had to uninstall it. I upgraded to the latest some weeks back and it wouldn't launch. I uninstalled and reinstalled several times, and it still wouldn't launch. It kept asking me to upgrade .NET Framework. I did that, still no dice. Is that fixed with the latest?

Thanks for this, and I've tried it. SourceTree still goes to 100% on the Mac, and when I open the log there's a bunch of 429 responses for Pipelines. We've seen an association with Pipelines for this issue. Maybe the 429s are making SourceTree spin internally? Perhaps queuing to try again? 

Know what's a great way to find deep-rooted bugs? Porting to another platform! Challenge your assumptions about how the OS and GUI toolkit should behave and you might discover the cause of all these crashes...

Debug -> Open Logs Folder doesn't even work. Come on guys.

On Mac, I get the rainbow cursor constantly. It's the only app I use that I know it doesn't (necessarily) mean it's crashed, you just have to go do something else for awhile and then it'll work again. Rinse and repeat for every action.

On Windows (10), a simple click on a file and the app thinks you're holding down and dragging. I have to slowly double click (so as not to open) a file to begin every selection process.

It really seems to me like Atlassian could care less about Sourcetree. It could be an app that gives Bitbucket a great advantage over competitors but, if anything, it's an example of why people shouldn't trust them.

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 23, 2018

@morungos There is a fix for cache misses with Pipelines in 2.7.4. Please file a ticket if you experience problems still.

We finally found the fix our massive performance problems with source tree. (taking 20mins to commit even a single file).  It turned out to be a conflict with the Antivirus that was blocking everything. 

A guide for configuring Antivirus programs to avoid performance issues would be nice.

Like Mark Schneider likes this

I stopped use SourceTree recently due to serious performance issues. Basically getting the rainbow beachball for even really simple operations. I still like the idea of having a GUI for visualizing branches and such, but I've found it was more of a crutch than a necessary tool. 

Gonchik Tsymzhitov
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 20, 2021

Thank you for that one, that's needful to our end users

Thanks, Nicholas.  I too found the problem to be with Antivirus.


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events