Commits scrollbar shown wrong number of items

[Alejandro Ariel Abaca]

The 3.4.27 Windows version in my computer shows the commits scrollbar with only 50-60 items when the repository has 3000 items. When I arrive to the last item, automatically, the scrollbar is reset to the top. So I can not view the history of the repository anymore. What's more painful is that my home's Mac Book Pro with SourceTree DOES show the complete scrollbar and I can see all the commits and its contents.

In the Windows computer, when I clic in an old branch whose first commit falls under the 50-60 items limit, the program enters in a cycle of "loading" events that never stops. The only way for me to put it to wrok again is clic in a new branch (one in which its first commit falls inside the 50-60 limit).

I did not have this problem before upgrading to 3.4.27 but, I must add, I followed a procedure to activate git-flow because it stopped functioning with this version. Me and another group of users posted that it was not working and Maria gave us that wotkaround.

Thanks.

Ariel.

[Tomislav Tobijas]

Hey @Alejandro Ariel Abaca ,

You could try reverting to 3.4.26 just to confirm that it appeared as an issue in the latest Windows version.
I've tried checking official bug tracker for Sourcetree, but couldn't find any open items related to this.

What you could do is create a new bug related to the behavior you're seeing. For on-prem/DC products, every user can create a new ticket (bug or suggestion) - you simply need to log in to the portal with the same account you're using here to raise a bug.

If you do so, feel free to share the link to the created item here. ➕

Cheers,
Tobi

[Alejandro Ariel Abaca]

Hi, Tomislav. And thanks for your answer and suggestion.

I have downgraded my SourceTree to version 3.4.26, the September 2025 version. Immediately my SourceTree started to behave as expected. I can see the scrollbar with a lot more items and, as I aproach the bottom end of the scrollbar, the program extends it with more items. That is the way it used to work.

Maybe I am having a setup that 3.4.26 works well with, but 3.4.27 does not?

I searched the configuration in SourceTree but cannot find anything that could change beahaviour this awful way.

I will be creating a case in the official bug tracker now, as you suggested.

Thanks in advance.

Regards.

Ariel.

[Tomislav Tobijas]

@Alejandro Ariel Abaca , I'm glad it looks okay with 3.4.26.

As for this:

Maybe I am having a setup that 3.4.26 works well with, but 3.4.27 does not?

It's probably an app/product bug rather than an issue on your end. That being said, creating a bug ticket will definitely help devs to take a look and troubleshoot it. 👀

[Alejandro Ariel Abaca]

As you requested I have created a bug/support ticket in the JIRA System: 

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

I have tried and write down my problem and the sugestion you have given (downgrade SourceTree to version 3.4.26 that did work).

Thank you very much for taking care.

Regards.

Ariel.

[Tomislav Tobijas]

@Alejandro Ariel Abaca, great. Thanks for sharing the link! Added my vote.

Hope this will be resolved quickly 🤞