That would be too severe of medicine; I would only like to fall back on that in desperation.
- HaroldFinch
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
--I downloaded the debug build from the link that you emailed me
--I extracted everything from its zip file
--I noticed that the extraction produced a WinSCP.exe direct executable file (i.e. the full program, NOT an installer)
--so, I double clicked on that WinSCP.exe file; all subsequent operations below were done with it
--NOTE: I did NOT uninstall my normal WinSCP install (5.5.6)
--I had already rebooted my machine last night, after the last time I used the 5.5.6 GUI
--I did not start up th 5.5.6 GUI so far today
--I opened Task Manager and looked under processes, and verified that no instance of 5.5.6 was running
--that debug WinSCP.exe instance was agonizingly slow!
--maybe 1000X slower than the normal build
--operations that should be < 1 sec can take > 1 minute...
--fortunately, the debug WinSCP.exe instance did pick up old settings, so login to my server was easy
--I redid the same exact Find File operation as described in my original post
--after several minutes, I clicked on the stop button to kill the search, and then I shut down the program
--NOTE: this time, when the search was going on, I did not see the path endlessly repeat at the bottom of the Find File dialog
*22559*
in my /sys
directory).
WinSCP_find_bug.png
file that I attached to this post shows what the Find Dialog looks like when it gets stuck.
/sys/devices/platform/pcspkr/subsystem
.
/sys/devices/platform/pcspkr/subsystem
is a link that points to ../../../bus/platform
.