Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
NetMage
283 discussion posts
Is there a reason the Settings dialog is very slow?

When I click to open settings it takes over 40 seconds to open, and opens behind other windows but the (DF) taskbar button isn't blinking.

When I make a change (like adding a compatiblity setting) and click Apply, the dialog shows a wait cursor, the main dialog buttons gray out for a few seconds, then come back, then the dialog moves a few pixels down and to the right and the Titlebar shows Not Responding for over 40 seconds.

I am on an nVidia video card with Windows 7 64-bit Enterprise behind a authentication required proxy server.
Jan 15, 2015 (modified Jan 15, 2015)  • #1
Keith Lammers (BFS)'s profile on WallpaperFusion.com
It definitely shouldn't take that long. Could you send me a backup of your settings so that I can test them out here?

Thanks!
Jan 16, 2015  • #2
User Image
NetMage
283 discussion posts
Sorry I hadn't looked at this in a while. It is still slow to open in 7.2.0 beta 2. Attached are my settings backup.
• Attachment [protected]: DisplayFusion Backup (2014-02-05 @ 15-40, 5.9.9.102, DRHSIS007D, Auto).reg [58,686 bytes]
Feb 26, 2015  • #3
Keith Lammers (BFS)'s profile on WallpaperFusion.com
No worries, just tested it out here and we got the same results. It looks like it's due to a Window Location rule for a program that's on a network share. Is your computer normally connected to that network share? The delay is likely due to DF trying to access the share but not being able to. As soon as we removed that rule from our test machine, the Settings window opened quickly :)
Mar 3, 2015  • #4
User Image
NetMage
283 discussion posts
The rule pointed to a server that was migrated to a new name. I changed the rule to use my mapped drive instead.

Perhaps the timeout could be reduced on that?

Thanks!
Mar 4, 2015  • #5
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Unfortunately not. We just use the normal .NET functions for accessing stuff on file shares, and .NET/Windows handles the connection and timeouts.

However, it looks like it may be possible to adjust the SMB timeout, with the "SessTimeout" registry value. See this page for details: http://blogs.msdn.com/b/openspecification/archive/2013/03/27/smb-2-x-and-smb-3-0-timeouts-in-windows.aspx

Hope that helps!
Mar 4, 2015  • #6
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(-)  Login to Vote(-)