Or the roll up animation might not have exited cleanly or caused some trouble for explorer (generating thumbnails, etc.) I also thought it could be something related to the triple desktop setup - I know the displays can be enumerated differently between Windows and Nvidia, which could have caused some odd condition. One or the other might get stuck updating or a file might get locked and set off a cascade. My suspicions were related to the navigation and details view. All fences set to classic view, all portals set to List. I disabled the roll-up fences feature entirely, moved all fences to the same display, removed 1 portal, and reduced the number of files/folders actually on the desktop to <10 per fence. Not sure what squashed it, but it was definitely not disabling a third party program or Windows/driver update. Responsiveness feels a bit more sluggish than without Fences (but we're talking <0.5 sec increase in icon selection time). Parts I'm fuzzy on - The views (swapped around between classic and medium for the fences and just about all of them for the portals. Desktop pages disabled, subset of fences and portals set to not hide with desktop double click, all snapping and spacing enabled (0 px), stored per screen layouts, All set to details view, navigation enabled, and roll-up tabs feature enabled. 3 portals had ~10 subfolders, ~20 files at root, 30-40 files per subfolder. Folder Portals: 1 portal had ~10 files. Standard fences: File counts were <25 each, a couple different views used, autosorting rules on (none custom), always visible 20%, fade to 90% on mouse over. Fences on Display 2 and portals on Display 3 (triple display setup). 4 standard fences and 4 folder portals. Disabling Fences within the options (I assume it runs that ps1 script?) immediately resolved the slowdown. Standard uninstall fences, reboot, delete remnants, reinstall sequence. Hardware and background programs listed at the bottom. Shutting down every background program and stopping all third party services had no effect. Killing explorer had no effect on the problem. Checking Process Explorer, no obvious issues - memory of the svchost attached to Fences was slightly higher (~35MB private, usually <20MB), but no CPU or IO spikes. CPU load high, not unusually high - 1 or 8 'cores' (4 core w/ hyperthreading) 15-20%. Could hear my fans spinning, but definitely not at max. Resembled a memory leak - increasing delay in response across ~3 hours. Installed 3.0.5 and got the slow down after a couple days. Used Fences way back in v1.0 days, but eventually uninstalled it and just came back (Humble Bundle last month). I don't have time to troubleshoot Fences, but I'll contribute what I can in this post. Not sure if I like the cringe-worthy in-your-face company rep responses of back then or canned corporate handwaving sans action of today more.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |