Tracker »
Issue 996 – Failure to run WinSCP or open session with .NET assembly after frequent scheduled use
:
.NET
:
5.0.8 RC
:
Bug
:
High
:
0
Emails with Paul Monteiro, Thomas Lexa, Vladimír Suchan
Associated error messages:
WinSCP.SessionLocalException: WinSCP process terminated with exit code 3 and output "", without creating a log file.
System.TimeoutException: Timeout waiting for WinSCP to respond - Log file C:\...tmp was not created in time, please make sure WinSCP has write permissions to the folder
WinSCP.SessionLocalException: WinSCP process terminated with exit code 3 and output "", without creating a log file.
System.TimeoutException: Timeout waiting for WinSCP to respond - Log file C:\...tmp was not created in time, please make sure WinSCP has write permissions to the folder
Emails with Mike Buland in April–May 2013.
Emails with Jason Terando in July 2013.
Emails with Todd Daniels in March–April 2013.
Emails with Pavel Fomichev in March 2013.
Emails with Ronald Broens in February 2013.
Emails with Jason Terando in July 2013.
Emails with Todd Daniels in March–April 2013.
Emails with Pavel Fomichev in March 2013.
Emails with Ronald Broens in February 2013.
Possibly related issue with winscp.com:
https://winscp.net/forum/viewtopic.php?t=12246
Emails with Eric Wong in March 2013.
https://winscp.net/forum/viewtopic.php?t=12246
Emails with Eric Wong in March 2013.
Issue 1012 has been marked as a duplicate of this issue.
Possibly related issue with inability to connect:
https://winscp.net/forum/viewtopic.php?t=12533
Emails with Ilja Verchenko in July 2013.
https://winscp.net/forum/viewtopic.php?t=12533
Emails with Ilja Verchenko in July 2013.
Everyone, please upvote my related question on StackOverflow:
https://stackoverflow.com/q/18893366/850848
https://stackoverflow.com/q/18893366/850848
Fixed.
The bug was always present in WinSCP. But until the WinSCP 5.0.8, with its "Dynamic base address" executable flag set (Windows 8 certification requirement), the bug happening was not plausible.
While the fixed versions no longer gradually exhaust system resources, they cannot recover resources exhausted by previous buggy versions. So it's still necessary to restart affected machine to recover the system.
Possibly related issue with inability to connect:
https://winscp.net/forum/viewtopic.php?t=13102
https://winscp.net/forum/viewtopic.php?t=13102
Inability to connect:
https://winscp.net/forum/viewtopic.php?t=12868
https://winscp.net/forum/viewtopic.php?t=12868
https://winscp.net/forum/viewtopic.php?t=12108