I have 3 entries in JumpList and no master password. It starts and runs without problems.
I receive the "Invalid access to memory" error message after network disconnects (when returning from sleep, for example.)
I enabled logging level 2 and extracted below several lines around the moment when the error message is displayed
. 2011-11-08 11:18:06.363 Read file 'export' from listing
. 2011-11-08 11:18:06.364 Waiting for another 4 bytes
. 2011-11-08 11:18:06.364 Looking for incoming data
. 2011-11-08 11:18:06.364 Looking for network events
. 2011-11-08 11:18:06.435 Detected network event
. 2011-11-08 11:18:06.435 Enumerating network events for socket 680
. 2011-11-08 11:18:06.435 Enumerated 1 network events making 1 cumulative events for socket 680
. 2011-11-08 11:18:06.435 Handling network read event on socket 680 with error 0
. 2011-11-08 11:18:06.435 Received 32 bytes (0)
. 2011-11-08 11:18:06.435 Read 4 bytes (28 pending)
. 2011-11-08 11:18:06.435 Read 28 bytes (0 pending)
< 2011-11-08 11:18:06.435 Type: SSH_FXP_STATUS, Size: 28, Number: 2572
< 2011-11-08 11:18:06.435 65,00,00,0A,0C,00,00,00,01,00,00,00,0B,45,6E,64,20,6F,66,20,66,69,6C,65,00,
< 2011-11-08 11:18:06.435 00,00,00,
< 2011-11-08 11:18:06.435 Status code: 1
> 2011-11-08 11:18:06.435 Type: SSH_FXP_CLOSE, Size: 13, Number: 2820
> 2011-11-08 11:18:06.435 04,00,00,0B,04,00,00,00,04,00,00,00,00,
. 2011-11-08 11:18:06.435 Sent 17 bytes
. 2011-11-08 11:18:06.435 There are 0 bytes remaining in the send buffer
. 2011-11-08 11:18:06.435 Looking for network events
. 2011-11-08 11:18:06.435 Timeout waiting for network events
. 2011-11-08 11:18:06.439 Startup conversation with host finished.
* 2011-11-08 11:18:06.442 (EAccessViolation) Access violation at address 0059D504 in module 'WinSCP.exe'. Read of address 00000000
. 2011-11-08 11:18:06.451 Session upkeep
. 2011-11-08 11:18:06.451 Looking for network events
. 2011-11-08 11:18:06.451 Timeout waiting for network events
. 2011-11-08 11:18:06.455 Session upkeep
I can send you the entire file if it helps you identify the problem (or you could send me the debug version if the log doesn't help.)
The problem is also present in 5.0.3. I am not sure about 5.0.1 and 5.0.2.