-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Highest
-
None
-
Affects Version/s: 3.4.27, 3.4.28
-
Component/s: General
-
None
-
Severity 2 - Major
I only recently updated SourceTree from 3.4.24 to the latest 3.4.28, because I'm always reluctant updating SourceTree, given I've had issues after updates with SourceTree before. And there is another issue once more. I really like SourceTree, but it seems updates regularly break the application for bigger repositories...
This issue is present in 3.4.28 and 3.4.27. It is NOT present in 3.4.26 or any earlier version. I've downgraded back to 3.4.26 after trying to freshly install the two latest versions to verify the issue. I've also cleared any caches before testing either version.
The problem is: SourceTree in >= 3.4.27 is completely unable to load earlier commits than the ones loaded during startup. If I set the "Log rows to fetch per load" to 500, then 500 commits can be loaded at startup. But if I attempt to scroll down and load the next 500 rows, SourceTree will end up in a death loop where it basically loads forever. The rows to fetch I configure have zero effect on this behaviour. I've tried to set it to 50, 25, 100, 200, 10000. Once I scroll down the History in SourceTree, the application becomes entirely unusable.
I've created a video here: https://dibitmesstechnik-my.sharepoint.com/:v:/g/personal/sebastian_holzer_dibit_at/IQAvkDrQPXwxRLxnfgRVuIwDAcSxB7bNVV9eMFzj2YMyk-4?e=efaSmp
Please note, I've waited nearly an hour to load 100 earlier commits. It never stopped loading.... This video is shorter, because SourceTree does not do anything else for the whole hour than seen in the video.
Additional Info: I'm on Windows 11 Pro 25H2. I'm using Git for Windows / System. I replicated the issue in two bigger repositories (lots of refs) even with the default settings. I tried alot of suggestions found via Google and given by Gemini/ChatGPT. Nothing helped at all. Since this blocks me from using SourceTree entirely (unless I set the rows to fetch to 50000, which surprisingly works, but takes some time to load at startup) I'd classify this as a Critical issue. But since apparently noone else is experiencing this, I've set it to Major.