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.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

paul_emil

Yes, I've already upgraded :) (and I saw in the v5.2.6-beta release notes that there was a bug-fix for an anonymous bug related to session closing).
Thanks!
martin

Re: Last version (5.2.5 beta) Invalid access to memory

Thanks for your report.
There's bug fix for failure when disconnecting session in 5.2.6 beta.
Please upgrade. Let us know if it ever happens again.
paul_emil

Last version (5.2.5 beta) Invalid access to memory

Version of WinSCP I'm using: the current latest --- WinSCP 5.2.5.

Version of Microsoft Windows I'm running WinSCP on: Windows 7 Enterprise SP1 64-bit.

Transfer protocol(s): SFTP.

I use GUI; interface style I'm using: Commander.

Describe precise steps that lead to the problem:
[Un]fortunately, I cannot reproduce it (nor can I give much details). I was trying to close few sessions opened on an AIX server before shutting down WinSCP. WinSCP was not configured to log its operations, so I cannot attach a session log file. Also,I can't provide a screenshot --- it happened too fast and did not repeat.


Error message:
Invalid access to memory.


Other data:
Some of the info mentioned above is summarized in the anonymous usage upload data -- see the attached file (WinSCP-v5.2.5-beta_anonymous-usage-upload-data_2013-11-14.lst).
PS: I was forced to put the data in a file because the it appears that the forum has the Scunthorpe problem with the s_ex word in the LifetimeRemoteFiles_Executed key (here, I've added an underline between "s" and "ex" to be able to announce this small inconvenience).