TC hangs then quits when trying to delete files

[bgergely]

Hi Christian,

Recently I've had issues when trying to delete files using TC. I've had this in an earlier version too (unfortunatelly do not have track of version), and then installed the then-available-latest version: 9.21a 64 bit (2018-08-21) but issue is still there.
When trying to delete, the "Deleting" popup window comes, stays at 0% all the time (few seconds, like ~5-7) and finally TC crashes (i'm saying crashes rather than quits, because when restarting it, it returns to previous start-up status). I tried updating to recent latest version (9.22) too and same behaviour happens. It happens regardless I run it as admin or not.
I can delete using Windows Explorer, also issue is not there when executing permanent delete.
I'm on a 64 bit Win 10.

Since it didn't start occuring after a TC refresh, also with latest update issue not disappearing, I'm suspecting it might be Windows as well, but thought would let you know.

Let me know if I can be of any help to you.

Thanks,
Gergely

[Dalai]

How exactly do you delete files? Del/F8, or Shift+Del/Shift+F8? How is your recycle bin set, does it show a confirmation? Can you reproduce this with a clean wincmd.ini? To do this, start TC like this:

Code: Select all

totalcmd64.exe /i="%temp%\fresh.ini"

Regards
Dalai

[ghisler(Author)]

Deleting to recycle bin is done with OLE2. This means that there is either a probklem with your OLE2 subsystem, or you have some kind of shell extension installed which is incompatible with Total Commander.

To analyze the crash, I need some kind of stack trace. Could you use the tool Procdump to create one for me, please:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows)
with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties the lnk file with Alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8. Send me the dump from c:\dumps. Please send only ONE(!) dump, and pack it with ZIP or RAR first. If it's smaller than 25MB, you may send it to my GMail account cghisler at gmail dot com. Otherwise please use a file sending service or web server and send me the URL.

[bgergely]

How exactly do you delete files? Del/F8, or Shift+Del/Shift+F8? How is your recycle bin set, does it show a confirmation? Can you reproduce this with a clean wincmd.ini? To do this, start TC like this:

Code: Select all

totalcmd64.exe /i="%temp%\fresh.ini"

Regards
Dalai

Hi Dalai,

I normally use Del, but now tried F8 also, same thing happens. I use Shift+Del for permanent delete, and tested for Shift+F8, it works seamless both ways.
Not sure of what you mean by confirmation on recycle bin, but items I try to delete, don't get moved to recycle bin when TC crashes.

I tried with clean wincmd.ini, same behaviour occurs with that as my own wincmd.ini.

Thanks,
Gergely

[bgergely]

Deleting to recycle bin is done with OLE2. This means that there is either a probklem with your OLE2 subsystem, or you have some kind of shell extension installed which is incompatible with Total Commander.

To analyze the crash, I need some kind of stack trace. Could you use the tool Procdump to create one for me, please:
https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

1. Create new directory c:\dumps
2. Create a lnk file of procdump.exe or procdump64.exe (for 64-bit Windows)
with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties the lnk file with Alt+Enter
4. Change the command from c:\path\procdump.exe to
c:\path\procdump.exe -ma -i c:\dumps
5. Important: Click on "Advanced" and check option "As administrator"
6. Run procdump with this link file
7. Wait until the crash occurs.
8. Send me the dump from c:\dumps. Please send only ONE(!) dump, and pack it with ZIP or RAR first. If it's smaller than 25MB, you may send it to my GMail account cghisler at gmail dot com. Otherwise please use a file sending service or web server and send me the URL.

Hi Christian,

Thanks for your time. Dump is available at https://bit.ly/2OwPOhz

Thanks,
Gergely

[ghisler(Author)]

Thanks for the crash dump. The crash happens in a file "COM_Sensor64", which seems to be part of a tool "Digital Guardian":
https://en.wikipedia.org/wiki/Digital_Guardian

Here is the full stack trace:

Code: Select all

STACK_TEXT:  
00000000`4f73d0a8 00007ffc`f1dacd0c : 00000000`000036b7 00000000`4f73d450 00000000`00000003 00007ffc`f6490480 : 0xffffffff`ffffdeb8
00000000`4f73d0b0 00007ffc`f40b794b : 00000000`000036b7 00000000`05940ae0 00000000`4f73d450 00000000`00000001 : COM_Sensor64!DGSetupSensor+0x3ca3c
00000000`4f73d110 00007ffc`f40b76bf : 00000000`4f73d270 00000000`8007000e ffffffff`fffffffe 00000000`057db970 : windows_storage!CFileOperation::_NotifyStartOperationsCallback+0x3b
00000000`4f73d140 00007ffc`f40c05f0 : 00000000`057db590 00000000`4f73d270 00000000`8007000e 00000000`058f3f60 : windows_storage!DPA_EnumCallback+0xb3
00000000`4f73d170 00007ffc`f40bfdef : 00000000`00000000 00000000`00000000 00007ffc`f40bfd40 00000000`00000035 : windows_storage!CFileOperation::StartOperations+0x1a0
00000000`4f73d640 00007ffc`f1dabaf0 : 00000000`00000000 00007ffc`f40bfd40 00000000`00000000 00000000`057db5a0 : windows_storage!CFileOperation::PerformOperations+0xaf
00000000`4f73d6a0 00000000`005c9b1e : 00000000`00000001 00000000`00000000 00000000`4f73fd60 00000000`00000039 : COM_Sensor64!DGSetupSensor+0x3b820
00000000`4f73d730 00000000`00000001 : 00000000`00000000 00000000`4f73fd60 00000000`00000039 00000000`4f73fd50 : TOTALCMD64+0x1c9b1e

Total Commander calls "IFileOperation->PerformOperations" to perform the delete, which then crashes in COM_Sensor64.dll : DGSetupSensor.

[bgergely]

Thanks so much for digging into this. This is something running as a company policy, so can't do much about it! :-\
Thanks for your help!

All the best,
Gergely

[ghisler(Author)]

You could try to report the bug to the makers of Digital Guardian. It should not cause other programs to crash, especially in standard system code on which I don't have any influence, like the delete functions.

Here is the function which crashes in Digital Guardian:
https://docs.microsoft.com/en-us/windows/desktop/api/shobjidl_core/nf-shobjidl_core-ifileoperation-performoperations

[bgergely]

Thanks for the suggestion! I submitted a ticket with them.