Re: Invalid Access to Memory
Please let me know if you find a way to reproduce the problem at will.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Guest
Invalid Access to Memory
Version 4.1.6 (Build 412)
After executing for a while, the program was in a standby state. Suddenly the Invalid Access to Memory dialog popped up. After clicking on OK, the dialog reappeared about every 5 seconds. In between, it was almost impossible to click on any other function or menu before a new dialog showed up. Finally, I was able to access the Protocol information. Surprisingly, the dialog stopped. I was able to transfer files as usual. I have had several "Invalid Access to Memory" popups in the past. Usually, they are after the operating system has been running for a while (probably more memory used but never freed). In these caess, the program never starts working properly again. so this time was odd that WinSCP settled down.
Session protocol = SSH-2
SSH implementation = OpenSSH_4.7
Encryption algorithm = aes
Compression = No
File transfer protocol = SFTP-3
------------------------------------------------------------
Server host key fingerprint
ssh-rsa 1024 32:5d:aa:fb:ed:1b:9c:12:32:67:68:89:95:74:1c:12
------------------------------------------------------------
Can change permissions = Yes
Can change owner/group = No
Can execute arbitrary command = No
Can create symlink/hardlink = Yes/No
Can lookup user groups = No
Can duplicate remote files = No
Can check available space = No
Can calculate file checksum = No
Native text (ASCII) mode transfers = No
------------------------------------------------------------
Additional information
The server does not support any SFTP extension.
After executing for a while, the program was in a standby state. Suddenly the Invalid Access to Memory dialog popped up. After clicking on OK, the dialog reappeared about every 5 seconds. In between, it was almost impossible to click on any other function or menu before a new dialog showed up. Finally, I was able to access the Protocol information. Surprisingly, the dialog stopped. I was able to transfer files as usual. I have had several "Invalid Access to Memory" popups in the past. Usually, they are after the operating system has been running for a while (probably more memory used but never freed). In these caess, the program never starts working properly again. so this time was odd that WinSCP settled down.
Session protocol = SSH-2
SSH implementation = OpenSSH_4.7
Encryption algorithm = aes
Compression = No
File transfer protocol = SFTP-3
------------------------------------------------------------
Server host key fingerprint
ssh-rsa 1024 32:5d:aa:fb:ed:1b:9c:12:32:67:68:89:95:74:1c:12
------------------------------------------------------------
Can change permissions = Yes
Can change owner/group = No
Can execute arbitrary command = No
Can create symlink/hardlink = Yes/No
Can lookup user groups = No
Can duplicate remote files = No
Can check available space = No
Can calculate file checksum = No
Native text (ASCII) mode transfers = No
------------------------------------------------------------
Additional information
The server does not support any SFTP extension.