Unfortunately, I can't intentionally reproduce this bug and winscp debug logging slow down my work.
Is this a known bug? What can I do to prevent it?
I've thought this has been fixed 1.5.1, hasn't it?I know it's been a while. Any new? :mrgreen:
Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.I tried three configs:
far2.0/vista/local user install
all used plugin 1.6.2
tried two hosts, same results.
in every scenario as soon as I tried editing a file with F4 (external editor, editplus) invalid memory access arised. which works just fine on loal files, no hassles. on vista, after error, I could use the internal viewer but on the xp both editing and viewing kept on throwing this error.
You can post new topics in this forum