Issue activity log

2013-04-24 13:04 Created Exit code 3 on frequent use of .NET assembly or scripting
Component .NET
Severity Bug
Priority High
Comment https://winscp.net/forum/viewtopic.php?t=12091
https://winscp.net/forum/viewtopic.php?t=12108
2013-04-24 13:07 Comment Emails with Paul Monteiro, Thomas Lexa, Vladimír Suchan
2013-07-04 15:28 Comment 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
Comment https://winscp.net/forum/viewtopic.php?t=12277
https://winscp.net/forum/viewtopic.php?t=12580
Comment 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.
2013-07-04 15:29 Comment Possibly related issue with winscp.com:
https://winscp.net/forum/viewtopic.php?t=12246
Emails with Eric Wong in March 2013.
Comment Issue 1012 has been marked as a duplicate of this issue.
Summary Exit code 3 on frequent use ofFailure to open session with .NET assembly or scriptingafter frequent scheduled use
2013-07-05 15:10 Comment Possibly related issue with inability to connect:
https://winscp.net/forum/viewtopic.php?t=12533
Emails with Ilja Verchenko in July 2013.
2013-07-07 08:45 Comment https://winscp.net/forum/viewtopic.php?t=11485
2013-07-23 16:28 Comment Documented related error messages:
https://winscp.net/eng/docs/message_library_process_terminated_with_exit_code_3
https://winscp.net/eng/docs/message_library_timeout_waiting_to_respond
2013-09-05 12:54 Comment https://winscp.net/forum/viewtopic.php?t=12838
2013-09-05 12:56 Summary Failure to open session with .NET assembly or WinSCP after frequent scheduled use
2013-09-16 12:19 Comment https://winscp.net/forum/viewtopic.php?t=12884
2013-09-19 14:28 Comment Everyone, please upvote my related question on StackOverflow:
https://stackoverflow.com/q/18893366/850848
2013-09-19 14:44 Comment https://winscp.net/forum/viewtopic.php?t=11975
2013-09-19 16:55 Summary Failure to run WinSCP or open session with .NET assembly or WinSCP after frequent scheduled use
2013-09-23 15:29 Resolution FIXED
Fixed in 5.2.5
Status RESOLVED
Comment Fixed.
2013-09-30 09:20 Comment The bug was always present in WinSCP. But until the 5.0.8, with its "Dynamic base address" executable flag set (Windows 8 certification requirement), the bug happening was not plausible.
Version 5.0.8 RC
2013-10-04 11:34 Comment https://winscp.net/forum/viewtopic.php?t=12941
2013-10-25 17:17 Comment https://winscp.net/forum/viewtopic.php?t=13005
2013-10-25 19:14 Comment 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.
2013-11-25 08:40 Comment https://winscp.net/forum/viewtopic.php?t=13099
2013-11-25 09:17 Comment Possibly related issue with inability to connect:
https://winscp.net/forum/viewtopic.php?t=13102
2013-11-25 18:05 Comment Inability to connect:
https://winscp.net/forum/viewtopic.php?t=12868
2013-12-10 18:28 Fixed in 5.2.5 → 5.1.8
2013-12-17 08:57 Comment https://winscp.net/forum/viewtopic.php?t=13179
2013-12-17 20:43 Comment https://winscp.net/forum/viewtopic.php?t=11719#48316
2013-12-24 08:35 Comment https://winscp.net/forum/viewtopic.php?t=13209
2014-01-02 09:11 Fixed in 5.1.8 → 5.2.5
2014-02-07 09:27 Comment https://winscp.net/forum/viewtopic.php?t=13467
2014-11-06 08:20 Comment https://stackoverflow.com/q/26771924/850848
2015-01-30 09:04 Comment https://winscp.net/forum/viewtopic.php?t=14797
2015-05-29 10:01 Comment https://winscp.net/forum/viewtopic.php?t=15436
2015-09-08 10:13 Comment https://winscp.net/forum/viewtopic.php?t=15859
2016-08-04 08:45 Comment https://winscp.net/forum/viewtopic.php?t=23272#71064
2022-06-16 09:25 Comment See Issue 2075.
2022-10-05 08:59 Comment 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.