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; } } }

Loading the commit history takes forever, but only on one computer

Uwe Risse

I have SourceTree installed on two computers, both with the identical content in terms of branches and settings. The history of my project goes back until 2005 with thousands of commits. On my older computer (Windows 10), everything is fast and smooth. On my four times faster computer (with Windows 11), however, the commit history stays at "Loading 120 commits to reach commit xyz" forever, when trying to reach older commits. Any idea where it comes from and how to fix this? Thanks!

Accepted answers

kku39

Hello,

I am experiencing the exact same issue with SourceTree version 3.4.27.0 on Windows 11.

As a temporary workaround, I have downgraded my SourceTree installation to version 3.4.26.0, and the issue is resolved in the older version. This suggests a bug specific to 3.4.27.0.

Hopefully, the development team can look into this soon.

Thanks.

All comments

Rock_696nbn

This is usually caused by a local issue, not the repo itself. On Windows 11, SourceTree can hang on history loading due to antivirus scanning, corrupted cache, or a Git performance setting.

Try clearing SourceTree’s cache, disabling real-time antivirus scanning for the repo folder, and make sure both machines are using the same Git version in SourceTree settings. In many cases, switching SourceTree to use the bundled Git instead of a system Git also fixes slow history loading.

kku39

Hello,

I am experiencing the exact same issue with SourceTree version 3.4.27.0 on Windows 11.

As a temporary workaround, I have downgraded my SourceTree installation to version 3.4.26.0, and the issue is resolved in the older version. This suggests a bug specific to 3.4.27.0.

Hopefully, the development team can look into this soon.

Thanks.

Uwe Risse

Hi, how did you downgrade? I would like to try this too.

Because none of the other proposed solutions braught any progress. Neither cloning the Atlassian folders at AppData/Local and AppData/Roaming from my older Win10 computer to my Win11 PC, nor starting SourceTree without AppData/Local/Atlassian folder so the program creates new entries and starts from the scratch, nor whitelisting the local repo at my antivirus software.

To me, it really seems that there is s a bug somewhere causing this incompatibility with Windows 11. Also for me, the issue started after updating SourceTree. However, I can't remember which update it was.

Regards

Uwe Risse

Bingo! Just installed 3.4.26.0 (downloaded from the Sourcetree Download Archives), and all works well again !!!

This means: There is definitely a bug in version 3.4.27 !!!!!

Thanks for your help, kku39!

Uwe Risse

Rock, how can we inform the Atlassian developers about this obvious bug in version 3.4.27? Because they should know, and fix this asap.

Uwe Risse

Just FYI: I have checked the SourceTree version istalled on my older Windows 10 computer. It was 3.4.23. This confirms that it is just the new version 3.4.27 that broke it.

I have therefore disabled the auto-update feature in all my SourceTree versions. Updates are of no use if they bring serious new bugs instead of useful new features or bug fixes.

kku39

It seems that this issue has already been reported on Atlassian's official bug tracker (Jira). You can check the status and add your comments here:

https://jira.atlassian.com/browse/SRCTREEWIN-14551

If you have an Atlassian account, I recommend clicking "Vote for this issue" on that page. It helps the developers understand how many people are affected and can speed up the fixing process.

Gianni Perugini

Hi all,

I'd like to point out that version 3.4.28 has the same issue.

Thanks

Regards

Gianni Perugini

Uwe Risse

Hi all,

Just an update. Meanwhile, SourceTree has become virtually unusable on my Windows 11 computer when I want to search for older commits. "Loading 120 commits to reach commit xyz" is then immediately displayed, and this stays forever.

First, it helped when I used the slightly older version from my Windows 10 computer (everthing just works fine there, btw.), but after a couple of days, the error suddenly reappeared, even with this slightly older version of SourceTree. I conclude from this that the root cause must be something else. But what?

Any solution would be really welcome!

Please fix this annoying bug !!!

Shawn Fox_wjeiqn

Unfortunately, SourceTree will automatically upgrade us again so it seems impossible to downgrade to 3.4.26 for very long.

Shawn Fox_wjeiqn

Most likely sourcetree upgraded itself and you have 3.4.28 again.

Shawn Fox_wjeiqn

Obviously, we cannot modify anti-virus settings on corporate computers so that is a non-starter.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

sourcetree

bitbucket

bitbucket-cloud