Memory leak/issues with 3.2, as well as 3.1.1

[John Paul Wilkens]

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.

[Jesika DiGregorio]

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.

[Theodore Gonzalez]

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

[John Paul Wilkens]

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