Slow startup with documents folder redirected to high-latency network drive

Create issue
Issue #155 resolved
Former user created an issue

With the default WinMerge settings (with the "user" filter directory being the default Documents directory) and with my Documents folder redirected to a "high"-latency network drive (~30 milliseconds ping) by my network admin WinMerge starts up very slowly (over a minute in my case). Almost all of that time is spent checking if each file in my Documents folder is a directory or not. Reversing the order of the checks in the loop in FileFilterMgr::LoadFromDirectory so that it first checks if the name matches the glob (none will in my case) before checking if the entry is a directory fixes the issue and causes WinMerge to start up nearly instantly.

Comments (3)

  1. Log in to comment