Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
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

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,559,193
Community Members
 
Community Events
184
Community Groups

Memory leak/issues with 3.2, as well as 3.1.1

Edited
John Paul Wilkens
John Paul Wilkens May 31, 2019

Edit: After updating to 3.2, same issue is happening.

Sourcetree has been consistently taking up ~110% of my computer's memory, and I have to keep killing it. Not sure what is causing it. It's almost unusable.

 

Screen Shot 2019-05-31 at 12.39.01 PM.pngScreen Shot 2019-05-31 at 12.40.41 PM.png

Answer
Watch
Like Be the first to like this
541 views

3 answers

0 votes
Jesika DiGregorio
Jesika DiGregorio Apr 03, 2020

I find that viewing files with a lot of changes slows things down drastically and that those resources are not release, even after that file is no longer being viewed in the UI. Even if that file is staged or otherwise removed from the list, the resources are still taxed. It is resolved by restarting SourceTree, but is a very frustrating issue.

 

I am running on Windows version 3.2.6 and was looking for a resolution to this and see that there isn't one in the release notes.

Reply
0 votes
Theodore Gonzalez
Theodore Gonzalez Feb 26, 2020

I'm using 4.0.1 and I still see SourceTree using 28GB of ram.

Reply
0 votes
John Paul Wilkens
John Paul Wilkens May 31, 2019 • edited Jun 10, 2019

Update: Updating app didn't resolve. Still have the leak happening.

I'm installing the update for now, but I'm sure there are people still using 3.1.1

I'll update back if I still have this issue with 3.2

Reply

Suggest an answer

Log in or Sign up to answer
Sourcetree
Sourcetree
TAGS
AUG Leaders

Atlassian Community Events

See all events