Re: Crash on renaming files immediately after upload
This issue has been added to tracker.
- 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
- Sigbjorn
Re: Crash on renaming files immediately after upload
I guess you are using editing mode Multiple files, use background transfer to upload changed files, are you?
Correct
- martin
Re: Crash on renaming files immediately after upload
Thanks, I'll check it. Just to be sure, I guess you are using editing mode Multiple files, use background transfer to upload changed files, are you?
- Sigbjorn
Crash on renaming files immediately after upload
Setup: version 3.82, Sftp and Norton style, WinXP Pro, Textpad as external editor
I have worked with a server reading (and caching files) lately, so I have created test files, and uploaded them. Every time I make a small change to a test file, I need to rename it so the server will make a fresh fetch instead of using the cached copy. So my workprocess is pretty much the following:
1 Open a file for edit
2 Do some changes
3 Close file and save changes
4 Rename file
5 Test file on server
6 Rename file
7 Open the file for edit
8 Save changes
9 Test file on server
10 Go to 2
In step 4, WinSCP often shows the following message in a popup
"Invalid access to memory"
How often depends on timing, if I wait long enough (till upload is properly finished and then a second more) it never happens. It seems to happen mostly when the renaming happens at the same time as the file is being uploaded or being closed on the server.
Sometimes there is just one popup, sometimes there is 2 or 3, and sometimes a cascade (I need to hold escape in for 10+ seconds to close them all - possibly one per file in the directory).
Sometimes the filenames in the directory blank out after this message, sometimes all of them, sometimes just a few.
Sometimes WinSCP disappears without a trace after these messages, and sometimes it crashes (is caught by the debugger on the system)
Attaching the start of a (custom built) crashlog, I'll upload/mail the full one if needed and told where to.
I have worked with a server reading (and caching files) lately, so I have created test files, and uploaded them. Every time I make a small change to a test file, I need to rename it so the server will make a fresh fetch instead of using the cached copy. So my workprocess is pretty much the following:
1 Open a file for edit
2 Do some changes
3 Close file and save changes
4 Rename file
5 Test file on server
6 Rename file
7 Open the file for edit
8 Save changes
9 Test file on server
10 Go to 2
In step 4, WinSCP often shows the following message in a popup
"Invalid access to memory"
How often depends on timing, if I wait long enough (till upload is properly finished and then a second more) it never happens. It seems to happen mostly when the renaming happens at the same time as the file is being uploaded or being closed on the server.
Sometimes there is just one popup, sometimes there is 2 or 3, and sometimes a cascade (I need to hold escape in for 10+ seconds to close them all - possibly one per file in the directory).
Sometimes the filenames in the directory blank out after this message, sometimes all of them, sometimes just a few.
Sometimes WinSCP disappears without a trace after these messages, and sometimes it crashes (is caught by the debugger on the system)
Attaching the start of a (custom built) crashlog, I'll upload/mail the full one if needed and told where to.
WinSCP3.exe 3.8.2.330 caused exception C0000025 at address 7C94EAFA (Base: 400000)
Registers:
EAX=0181F584 EBX=0181FFB0 ECX=00000000 EDX=7C90EB94 ESI=0181F600
EDI=00000000 EBP=0181F5E8 ESP=0181F578 EIP=7C94EAFA FLAGS=00000202
CS=001B DS=0023 SS=0023 ES=0023 FS=003B GS=0000
FPU stack:
3FFE8000000000000000 403ADE0B6B3A76400000 FFE07FFDF6CC7FFDF700
5D22B74EC9D880565CEC CDD87FFDF0000012FFE0 CD64B74ED000B74EC978
F700B74EC928FFFFFFFF 2490B74EC968827CEB30 SW=0000 CW=1372
Stack dump:
...