I just had Core FTP totally shut down my Windows 2000 Pro machine.
I had come back from lunch (after a few hours), and went to transfer a file from local to remote, and when I dragged the file onto the target folder I saw a CWD /home/.../target, and then it just sat there for a few. Usually when this happens I can seem to force a reconnect and have the file transfer automatically by hitting the disconnect button. So I hit disconnect and try to reconnect, and this is what I see in the log:
Network error: socket operation on non-socket (~ 7 million times)
I saw a few red words flash by in the log, but due to the infinte loop printing out the above message at the rate of about 1 every picosecond, I was not able to read what it was trying to tell me.
During the loop, all other programs running reported memory errors and crashed, and I was not able to close Core FTP or execute any Windows functions (minimize to desktop ran out of memory). I also got about 10 virtual memory errors stating that I needed more (memory, not errors). I also could not invoke the task manager in any way I tried. I had to shut down and log off via ctrl-alt-del to get Windows to regain control.
This seems like a fault of Windows. If I want to give a process 0 cycles I should be able to, but Windows knows what's best apparently.
Anyway, I am using 1.3 build 1403 ansi. See the thread titled "SFTP File Upload Errors" for more information on my system.
I have not reproduced this error, because I'm not hungry yet for lunch again. Even if I could reproduce it, I don't think I would.
infinite loop causes computer to asplode
I was able to replicate this on accident, but I was paying attention to what I was doing. The exact procedure, was that I had previously connected to a server via SFTP, and eventually it timed out. I came back after it had timed out, and dragged a file over to upload it. It popped up a couple messages in the log (not sure which ones) like the STOR command, and then just sat there. I hit the red disconnect button, and that prompted the infinite loop. This time however I was able to kill the process before it asploded.