FlashFXP Forums - View Single Post

Yil · 04-03-2007, 03:01 PM

Didn't get time to work much after tracking down the encoding issue, but I did give ioFTPD the ability to send data immediately instead of through it's normal more complex buffer handling (essentially the same as iputs --nobuffer). The problem is a recursive chmod/chown, site size or a move on a large directory all could take more than 2 minutes which is the default for FlashFXP I think disconnecting you. The command would be working just fine but get disconnected because it was unresponsive (saw it in a post here and in my debugging of a VERY large directory move). I'm not sure if I'll try to set a formal timer through ioFTPD's job scheduler (that would be best) or just embed a time test in the copy/change loop (currently testing like this). For the record Raiden just uses the shell copy command so it times out as well on a large move and at least on my copy it actually popped up a window showing a regular file move as if I had done it from explorer LOL.

I'm still debating the way to handle the encoding issue, but I think I'll try renaming the file to ascii7 and see if that fixes things. While this would break an official TCL script it would keep compatibility with existing iTCL scripts which is more important.

Peep: The address your giving for a crash is inside UpdateDirectory() which is a pretty complex beast that handles a lot of stuff. I'll pull up the debugger and track down line that is causing the exception and see where that leads. I'm particular annoyed that it's crashing for you. Keep the info coming if you are seeing other exception addresses. I'm guessing that the problem you found is likely the same as other peoples random crashes.

Update: The more info about what you were actually doing when a crash came (like peep's FTP log) or the test cases some of you have provided really make things easier for me.

Tuff, you mean ioFTPD-6.0.2.exe ? Hehe, the free versions HAD to be named ioFTPD.exe to work. I've added the actual build info into the executable's resource so if you hold your cursor over the file or open up the properties you'll see the build info.

04-03-2007, 03:01 PM
Yil Too much time... Join Date: May 2005 Posts: 1,194	Didn't get time to work much after tracking down the encoding issue, but I did give ioFTPD the ability to send data immediately instead of through it's normal more complex buffer handling (essentially the same as iputs --nobuffer). The problem is a recursive chmod/chown, site size or a move on a large directory all could take more than 2 minutes which is the default for FlashFXP I think disconnecting you. The command would be working just fine but get disconnected because it was unresponsive (saw it in a post here and in my debugging of a VERY large directory move). I'm not sure if I'll try to set a formal timer through ioFTPD's job scheduler (that would be best) or just embed a time test in the copy/change loop (currently testing like this). For the record Raiden just uses the shell copy command so it times out as well on a large move and at least on my copy it actually popped up a window showing a regular file move as if I had done it from explorer LOL. I'm still debating the way to handle the encoding issue, but I think I'll try renaming the file to ascii7 and see if that fixes things. While this would break an official TCL script it would keep compatibility with existing iTCL scripts which is more important. Peep: The address your giving for a crash is inside UpdateDirectory() which is a pretty complex beast that handles a lot of stuff. I'll pull up the debugger and track down line that is causing the exception and see where that leads. I'm particular annoyed that it's crashing for you. Keep the info coming if you are seeing other exception addresses. I'm guessing that the problem you found is likely the same as other peoples random crashes. Update: The more info about what you were actually doing when a crash came (like peep's FTP log) or the test cases some of you have provided really make things easier for me. Tuff, you mean ioFTPD-6.0.2.exe ? Hehe, the free versions HAD to be named ioFTPD.exe to work. I've added the actual build info into the executable's resource so if you hold your cursor over the file or open up the properties you'll see the build info.