Very slow (tortoise)SVN compare to base since win 10 Fall Creators Update [Local Repo]?

Question

I\'ve noticed an immense delay (just sitting there doing nothing) since upgrading to the latest version of windows while using tortoiseSVN to compare any file to its base ve

Answer 1

It did a trick for me. I allowed TortoiseSVN program in my antivirus firewall protection settings. It made SVN Commit fastest.

Go to your antivirus. I have Quick heal. So I will tell you the steps accordingly.

1) click on "Internet & Network"

2) Click on "Firewall protection"

3) Check for "Program rules" and click on "Configure" button. It will open a window displaying the list of allowed Exe on your system. Your antivirus blocks tortoiseSVN and related exes, if they are not in allowed Exe list.

4) So now click on "add" button, open dialog box will popup.

5) Go to "C:\Program Files\TortoiseSVN\bin" directory

6) Select TSVNCache.exe, TortoisePlink.exe, TortoiseProc.exe, ConnectVPN.exe And click "open" then click OK in list window.

Here you go. Hope it helps you.

Answer 2

In the TortoiseSVN settings window, I

1. selected Diff Viewer/Merge Tool section

2. checked External

3. selected WinMerge.

Works like a charm.

Answer 3

After installing 2018-01 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4058258) the speed problems for WinMerge appear to be completely fixed.

Answer 4

Instead of removing the "ribbon" setting, or changing security in Windows, I installed the last nightly build (1.9.9.x), and the performance is back. I looked at the settings, and the ribbon is still checked as default. But the performance is there. https://nightlybuilds.tortoisesvn.net/latest/x64/full/

Answer 5

The issue is already reported to Microsoft and Microsoft fixed in in Visual Studio 2017 15.6 when you recompile your code. Here the fixed MFC without the slow Get/SetPixel is used.

To fix in in Windows 10 for current and older compiled tools which use MFC, Microsoft released the Update KB4058258. The release notes don't mention the fix, but it is confirmed by the reporter that the fix is part of the cumulative update.

So installing the Update should fix it. So if you have the issue, make sure you run at least Build 16299.214 (run winver.exe to see the number).

If you have this or a higher number at last position, the issue should be gone.

The old and outdated information are archived. See the revisions of this answer for the old workarounds.

Answer 6

As a workaround, you can use the TortoiseUDiff tool instead. It is still fast. Here is what I do:

1. Right-click a working folder in Windows Explorer and click 'SVN Commit'
2. Select one or more files in the 'Commit > Changes made' list
3. Right-click the selection and select "Show changes as unified diff"

It's not as powerful as TortoiseMerge, but if you just need to see the changes you are committing, the above method still works fast.