Crash when retrying folder renaming on network share

Please report only one bug per message!

Moderators: white, Hacker, petermad, Stefan2

Post Reply
Moritz Kroll
Junior Member
Junior Member
Posts: 7
Joined: 2010-10-12, 10:05 UTC

Crash when retrying folder renaming on network share

Post by *Moritz Kroll »

Often when I try to rename a folder, it fails as some process still holds a handle to it. Since lately there's this nice retry dialog for this situation.
But sometimes (happened already 3 times) TC crashes when I closed the according processes and retry it:

Code: Select all

---------------------------
Total Commander 7.56a
---------------------------
Access violation at address 0067DEF0. Read of address 00000034.
Access violation at address 0067DEF0. Read of address 00000034
Windows Vista SP2 6.0 (Build 6002)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
0067DEF0
442F4F  445316  444F62  422CC0  444523  422CC0
444491  422CC0  444491  422CC0  431C3F  425870
444491  422CC0  444F62  422CC0  444491  422CC0
431C3F  444523  422CC0  444491  422CC0  444491
422CC0  431C3F  444523  422CC0  551D16  465F48
4662F8  443011  444F62  >422CC0  444523  422CC0
428268  428424  6C53C9  
Raw:
576C3D  444F62  444F85  402E36  443011  445231
4445E5  442F4F  445316  4456BA  443011  445231
4348C2  4445E5  444F62  444F85  422CC0  444523
422CC0  444491  422CC0  4452DB  444491  422CC0
4452DB  431C3F  443011  445231  4445E5  442F4F
425870  426C18  4255E6  446A93  576461  5764D1
444523  422CC0  63FFFE  62002C  5468FB  63FFFE
68593E  5F9A09  5475D7  443011  445231  42499C
4445E5  444F62  444F85  422CC0  4D002D  62002C
4452DB  443011  445231  4445E5  4348C2  4445E5
The folders are mounted network shares.
Moritz Kroll
Junior Member
Junior Member
Posts: 7
Joined: 2010-10-12, 10:05 UTC

Post by *Moritz Kroll »

Sometimes I'm able to reproduce it, when I open a cmd.exe with a command line antivirus scanner in the folder, then try to rename and get the error message, abort the scanner and close cmd, click on OK in the error message and OK in the rename dialog.
I wasn't able to reproduce it with just cmd.exe, yet, but I didn't try too many times...
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

How exactly do you start the rename function?
- Right click menu - Rename
- Shift+F6
- Slow double click on file?

If you get the error with the first, can you try to reproduce it also with the other two methods, please?
Author of Total Commander
https://www.ghisler.com
Moritz Kroll
Junior Member
Junior Member
Posts: 7
Joined: 2010-10-12, 10:05 UTC

Post by *Moritz Kroll »

I use cm_RenameSingleFile which I mapped to F2. This should be equivalent to Shift+F6, right?
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Yes, that shouldn't cause any problems. Do you use one of the "watch directory changes" options (Configuration - Options - Refresh, lower part)? Maybe something is causing the directory to change just when you try to rename that file?
Author of Total Commander
https://www.ghisler.com
Moritz Kroll
Junior Member
Junior Member
Posts: 7
Joined: 2010-10-12, 10:05 UTC

Post by *Moritz Kroll »

Yes, the first two and the last two options under "Auto-Refresh when the file system changes" are set, and one unrelated drive is excluded.
Indeed, the command line scanner is creating a log file, which regularly triggers a directory change (open, write line, close, open, write line, close, ...). But as long as it's running, the directory is locked, so renaming won't work anyways. Perhaps the last change event after closing the scanner is delayed until I click on OK in the rename dialog?
Moritz Kroll
Junior Member
Junior Member
Posts: 7
Joined: 2010-10-12, 10:05 UTC

Post by *Moritz Kroll »

I just also got this crash, when renaming a file on a mounted network share, which was still memory mapped by another application. It said, it cannot rename, I closed the other application, confirmed two times in TC and then it crashed. I think I saw a directory refresh right at the time it crashed.

---------------------------
Total Commander 7.56a
---------------------------
Access violation at address 0067DEF0. Read of address 00000034.
Access violation at address 0067DEF0. Read of address 00000034
Windows Vista SP2 6.0 (Build 6002)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
0067DEF0
551D16 465F48 4662F8 443011 444F62 >422CC0
444523 422CC0 428268 428424 6C53C9
Raw:
576C3D 5F006C 402E36 443011 445231 4445E5
442F4F 445316 4456BA 443011 445231 4348C2
4445E5 5F006C 444523 422CC0 444491 422CC0
4452DB 444491 422CC0 4452DB 431C3F 443011
4445E5 442F4F 425870 426C18 4255E6 446A93
576461 5764D1 443011 445231 42499C 4445E5
444F62 444F85 422CC0 5F006C 5475D7 443011
445231 42499C 4445E5 444F62 444F85 422CC0
4D002D 4452DB 443011 445231 4445E5 4348C2
4445E5 5F006C 5F006C 444491 422CC0 4452DB
Moritz Kroll
Junior Member
Junior Member
Posts: 7
Joined: 2010-10-12, 10:05 UTC

Post by *Moritz Kroll »

I recently got these crashes also for local folders (on a TrueCrypt mount) a few times, when trying to rename a folder, when it was still opened by other applications (for example, cmd.exe with current directory in this folder):

Code: Select all

---------------------------
Total Commander 7.56a
---------------------------
Access violation at address 0067DEF0. Read of address 00000034.
Access violation at address 0067DEF0. Read of address 00000034
Windows 7 SP1 6.1 (Build 7601)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
0067DEF0
576C3D  551D16  465F48  4662F8  443011  444F62
>422CC0  444523  422CC0  428268  428424  6C53C9

Raw:
576C3D  67006C  4452DB  43FFFE  445231  4445E5
442F4F  445316  4456BA  443011  445231  4348C2
4445E5  444F62  444F85  422CC0  444523  422CC0
444491  422CC0  67006C  444491  422CC0  4452DB
431C3F  443011  445231  4445E5  442F4F  425870
426C18  4255E6  446A93  576461  5764D1  67001E
5475D7  443011  445231  42499C  4445E5  444F62
444F85  422CC0  4D002D  4452DB  443011  445231
4445E5  4348C2  4445E5  63FFFE  444523  422CC0
551E60  444491  422CC0  4452DB  443011  445231
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 48021
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

This should be fixed in Total Commander 7.57 release candidate 1. It would be great if you could check that before TC 7.57 will be released.
Author of Total Commander
https://www.ghisler.com
Post Reply