Source Tree is now extremely slow to detect changes in the files for a project.
I have noted that both remote changes and local file changes are much slower to be detected thatn previously.
Anyone else feel me?
This issue is affecting me too. Really started slowing down when I updated. On 2.7.1 for Mac.
Refresh (cmd-R) is a lifesaver but it's still really a slowdown on the workflow. Fix for this is important.
Hi everyone! I've talked to our developer team about this issue and they told me they're currently looking into this and that you might expect an improvement shortly :)
Please bear with us in the meantime!
Regards,
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ana,
I was just wondering whether this issue is resolved or not as I am still seeing this issue in the latest version i.e. 2.6.3
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had some manual steps to go through that resolved the issue for me. They involved wiping the SourceTree system preferences. There is an article on it here:
This worked for me. Uninstalling and reinstalling doesn't affect these files.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dylan,
yes I have tried that option (deleting preferences) too but the issue is still occurring.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
*BUMP* - still an issue in 2.3.5
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am having this issue as well on 2.3.1.0
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Im using Version 2.1.10.0 on Windows 10. I have 13 Repo Tabs active
Its only since the update i have noticed a change i often get checkins that dont include all changed files, left over files are detected after commit.
Similar happens to all of my team.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ryan! Which kind of changes did you notice to go slower? Can you check what is the time you have set in the preferences for SourceTree to check for updates in the repos?
Also, remember to provide which SourceTree version and OS are you using so we can troubleshoot this issue better.
Best regards,
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ana,
+1 for me with this issue. Also version 2.1.10.0, since my machine updated on Friday (18 Aug 2017).
Windows 10 64-bit 1703 (build 15063.540)
When I make a change to my working copy, SourceTree basically doesn't seem to notice until I hit F5 to refresh, when the change is instantly picked up. Before the recent update SourceTree would see changes effectively instantly (when switching to the app, and once I had checked the "refresh when application is not in focus" even when I didn't; both "refresh automatically" and "refresh when not in focus" are currently checked).
A UI action, like e.g. staging a changed file also triggers an instant refresh.
NB nothing to do with remote repos.
Let me know if I can give any more info, or do anything else.
Cheers!
Richard
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nice tip about using F5. I never realised this works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you :) - F5 works well :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.