Issue activity log

2008-01-04 16:59 Created "Timeout waiting for external console" message
Component Scripting
Severity Enhancement
Comment https://winscp.net/forum/viewtopic.php?t=4418
https://winscp.net/forum/viewtopic.php?t=4202
Severity Enhancement → Bug
Comment I still need other people having the problem to contact me (on the forum threads above)
2008-12-05 16:52 Comment In at least one instance the problems occurred as follows:

WinSCP console interface was started from within another application, which redirects output (possibly also input) of the console to some kind of stream, so it can read it.
Problem is that the application waits for WinSCP console process to terminate before starting reading.
The stream created by the application has buffer of some size. So once WinSCP writes enough output, so the buffer gets filled, WinSCP console interface hangs on the next attempt to write. Consequently WinSCP times out waiting for the console interface to complete the write request and reports an error.
2008-12-09 08:28 Comment The above solution confirmed by at least one user:
https://winscp.net/forum/viewtopic.php?t=6375
2009-05-25 08:57 Comment Guide for using WinSCP from .Net discusses this issue as well:
https://winscp.net/eng/docs/guide_dotnet
2010-08-14 12:50 Comment See also example of WScript.Shell code:
https://winscp.net/eng/docs/guide_automation_advanced#inout
Status RESOLVED
Resolution INVALID
Comment Closing (not a bug).
2010-09-16 21:38 Comment Separate article on the topic:
https://winscp.net/eng/docs/message_timeout_external_console