[9.21a] (x64) Crash when copying the same folder to two destinations at the same time

[bogdanl]

I am trying to copy a single folder (which contains over 13000 C++ header files and 21000 folders) by using Ctrl+C in the source and then pasting (using Ctrl+V) in two or more destinations at the same time (or even pasting multiple times in the same destination). The copy operation begins, a window with the progress appears and then after a while TC crashes (Total Commander has stopped working).

If I paste to a single destination at a time, the copy operation completes successfully.

I am using TC 9.21a x64 on Windows 10 Enterprise 64-bit, version 1709.

This issue seems to reproduce every time with copy operations that take longer than a few seconds. Please let me know if I can be of any help debugging it.

[Horst.Epp]

And why do you use Ctrl-C and not a normal TC copy function for such a large tree ?

[petermad]

2bogdanl
If you use Ctrl+C -> Ctrl+V for copying, then the copying is done by Windows not by TC.

[Dalai]

2bogdanl
Well, you could try the same in Windows Explorer. If the copy process behaves the same there, the issue is not related to TC, and is most likely somewhere in your system.

Regards
Dalai

[bogdanl]

And why do you use Ctrl-C and not a normal TC copy function for such a large tree ?

I was expecting this kind of question It was just more comfortable at that moment, I have no better answer than that.

If you use Ctrl+C -> Ctrl+V for copying, then the copying is done by Windows not by TC.

I thought about that, but then why would TC crash?

Well, you could try the same in Windows Explorer. If the copy process behaves the same there, the issue is not related to TC, and is most likely somewhere in your system.

Well, I just tried doing the same with Windows Explorer, and it also crashes. So the problem does seem to be somewhere else. Should have checked that before pointing fingers

But the question remains: why would TC crash if Windows is doing the copying?

[bogdanl]

Oh well... I tried doing the same on another Windows 10 machine and there was no problem, so it appears that there's something wrong on my system.

If anyone is interested, here's what Event Viewer shows when explorer.exe crashes:

Code: Select all

Faulting application name: Explorer.EXE, version: 10.0.16299.637, time stamp: 0xd1134b58
Faulting module name: ntdll.dll, version: 10.0.16299.665, time stamp: 0x2e74e364
Exception code: 0xc0000374
Fault offset: 0x00000000000f842b
Faulting process id: 0x45d8
Faulting application start time: 0x01d469c5f98aaaca
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: b673b179-959e-4b66-a869-d65463e831e9
Faulting package full name: 
Faulting package-relative application ID: 

If TC also uses ntdll.dll, then that would explain why TC crashes when copying folders the unholy way

[Dalai]

TC crashes because the copying is done in the TC process context, although the copy itself is not done by TC. The crash might be caused by some shell extension.

Regards
Dalai

[bogdanl]

Yes, I agree. I'll just have to look through each shell extension to find the trouble maker. Thank you for your prompt assistance!

[Dalai]

ShellExView can assist in finding the culprit (if it is caused by a shell extension). You should begin by disabling non-Microsoft extensions.

Regards
Dalai

[ghisler(Author)]

I also suspect a faulty Explorer extension, especially since it also occurs in Explorer.

Here are the instructions for ShellExView:
1. Get the free tool ShellExView:
http://www.nirsoft.net/utils/shexview.html
2. Start it. If using Total Commander 32-bit, you need to get the 32-bit version, otherwise the 64-bit version of ShellExView. The 32-bit
version needs to be called like this: shexview.exe /wow64
3. Sort the shell extensions by type
4. Disable all context menu shell extensions one by one (you can hide/keep those made by Microsoft, they are usually OK).
5. Continue until Total Commander stops crashing
6. Now you can re-enable the extensions which don't cause any problems

[bogdanl]

Unfortunately that didn't help. I disabled all 5 non-Microsoft extensions and the problem remains. I'll try to get a crash dump of explorer.exe and see if that shows anything useful.

[ghisler(Author)]

Try disabling and re-enabling also all Microsoft extensions. This sometimes fixes bugs in the registry.