[8.0ß13-x32] Event log entries: TC crash without real crash

The behaviour described in the bug report is either by design, or would be far too complex/time-consuming to be changed

Moderators: Hacker, petermad, Stefan2, white

Post Reply
User avatar
Flint
Power Member
Power Member
Posts: 3506
Joined: 2003-10-27, 09:25 UTC
Location: Belgrade, Serbia
Contact:

[8.0ß13-x32] Event log entries: TC crash without real crash

Post by *Flint »

A user on the Russian forum reported that on his machine TC produces Event log entries about crashes, though no real crashes occur.

Sample log entry:

Code: Select all

Type : Error 
Date : 20/12/2011 
Time : 13:00:59 
Event : 1000 
Source : Application Error 
Category : Application Crashing Events 
User : N/A 
Computer : VVS-WORK.blag.local 
Description: 
Faulting application name: TOTALCMD.EXE, version: 8.0.0.0, time stamp: 0x2a425e19 
Faulting module name: shell32.dll, version: 6.1.7601.17678, time stamp: 0x4e5c6371 
Exception code: 0xc0000005 
Fault offset: 0x00250c6e 
Faulting process id: 0xd7c 
Faulting application start time: 0x01ccbedcbcb283ce 
Faulting application path: C:\Program Files\totalcmd\TOTALCMD.EXE 
Faulting module path: C:\Windows\system32\shell32.dll 
Report Id: 2209e088-2ae9-11e1-947f-0018f34520dc
Several crash dumps from him: http://people.sald.ru/vvs/tc_dmp.zip
Flint's Homepage: Full TC Russification Package, VirtualDisk, NTFS Links, NoClose Replacer, and other stuff!
 
Using TC 11.03 / Win10 x64
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50532
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I will check it - maybe TC is catching the exceptions, or it's some dll injected into TC which crashes.
Author of Total Commander
https://www.ghisler.com
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50532
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

I have analyzed it now - it's a strange crash in function CoUninitialize. The function is called at the end of the delete thread of the VistaDelete function.

Here is the stack trace:

Code: Select all

0262dc10 76b3121d 02cd9390 0262dc30 76b34047 shell32!CProgressDialogBridge::~CProgressDialogBridge+0x1b
0262dc1c 76b34047 00000001 0022e824 0022e768 shell32!CProgressDialogBridge::`scalar deleting destructor'+0xd
0262dc30 75f3bd44 02cd9390 ac7f572f 0022e76c shell32!CProgressDialogBridge::Release+0x27
0262dc70 75f3a71d 0262dcbc 00000001 00000000 ole32!CStdIdentity::ReleaseCtrlUnk+0x55
0262dc9c 75f15d00 00000008 00000000 760478f8 ole32!CStdMarshal::Disconnect+0x298
0262dcb0 75f15ce1 0262dcbc 0022e76c 00000008 ole32!DisconnectSwitch+0x16
0262dcc8 75f15d3f 00000008 00250130 fffffffe ole32!CStdMarshal::DisconnectAndRelease+0x44
0262de78 75f48f82 ac7f55e3 00250130 00000080 ole32!COIDTable::ThreadCleanup+0xcb
0262debc 75f48ec3 00000000 0262df0c 76047724 ole32!FinishShutdown+0x9d
0262dedc 75f49652 00000000 0000001f 00250130 ole32!ApartmentUninitialize+0x96
0262def4 75f488e8 0262df0c 00000000 7fffffff ole32!wCoUninitialize+0x88
0262df10 006baa06 00000000 00000000 03ea00ec ole32!CoUninitialize+0x72
0262ff5c 00417b56 00000000 00000000 03ea0128 TOTALCMD+0x2baa06: tVistaDeleteThread.Execute
0262ff74 0040361a 0262ffc4 00403470 0262ff88 TOTALCMD+0x17b56: ThreadProc
0262ff88 7617ed6c 03ea0128 0262ffd4 777837f5 TOTALCMD+0x361a: ThreadWrapper
0262ff94 777837f5 03ea0128 7519ee11 00000000 kernel32!BaseThreadInitThunk+0xe
0262ffd4 777837c8 004035f0 03ea0128 00000000 ntdll!__RtlUserThreadStart+0x70
0262ffec 00000000 004035f0 03ea0128 00000000 ntdll!_RtlUserThreadStart+0x1b
I have used this function many times, but cannot find any crash reports in the MiniDump folder.

Could you ask the user what he is deleting when he gets this error, please?
Author of Total Commander
https://www.ghisler.com
VVS
Junior Member
Junior Member
Posts: 3
Joined: 2011-12-22, 17:25 UTC

Post by *VVS »

ghisler(Author) wrote:I have analyzed it now - it's a strange crash in function CoUninitialize. The function is called at the end of the delete thread of the VistaDelete function.

I have used this function many times, but cannot find any crash reports in the MiniDump folder.

Could you ask the user what he is deleting when he gets this error, please?
Sorry my English...
I'm this user.
It's very difficult to catch this situation.
Does dump created with procdump with options -ma -e can help you?
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50532
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

No, I already know where it happens - in Windows function CoUninitialize. I just don't know why. I have added some more code now to uninitialize the delete objects, maybe that helps.
Author of Total Commander
https://www.ghisler.com
VVS
Junior Member
Junior Member
Posts: 3
Joined: 2011-12-22, 17:25 UTC

Post by *VVS »

ghisler(Author) wrote:No, I already know where it happens - in Windows function CoUninitialize. I just don't know why. I have added some more code now to uninitialize the delete objects, maybe that helps.
Sorry, but:
Type : Error
Date : 23/12/11
Time : 23:31:32
Event : 1000
Source : Application Error
Category : Application Crashing Events
User : N/A
Computer : VVS-Home
Description:
Faulting application name: TOTALCMD.EXE, version: 8.0.0.0, time stamp: 0x2a425e19
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000048
Faulting process id: 0x1568
Faulting application start time: 0x01ccc1a4863012a1
Faulting application path: C:\Program Files (x86)\totalcmd\TOTALCMD.EXE
Faulting module path: unknown
Report Id: b792025a-2d9c-11e1-b682-00158319de23
:(
VVS
Junior Member
Junior Member
Posts: 3
Joined: 2011-12-22, 17:25 UTC

Post by *VVS »

Hm...
TC 8 beta 14
I have Win7 with UAC enables and I works with user's rights.
Some minutes ago I deleted file from C:\Program Files\...
Windows asked me about privileges elevation, I entered admin's password and deleted file.
After what:
Type : Error
Date : 24/12/11
Time : 22:21:15
Event : 1000
Source : Application Error
Category : Application Crashing Events
User : N/A
Computer : VVS-Home
Description:
Faulting application name: TOTALCMD.EXE, version: 8.0.0.0, time stamp: 0x2a425e19
Faulting module name: shell32.dll, version: 6.1.7601.17678, time stamp: 0x4e5c6371
Exception code: 0xc0000005
Fault offset: 0x00250c6e
Faulting process id: 0xec0
Faulting application start time: 0x01ccc2589480c55e
Faulting application path: C:\Program Files (x86)\totalcmd\TOTALCMD.EXE
Faulting module path: C:\Windows\syswow64\shell32.dll
Report Id: 106fd819-2e5c-11e1-8751-00158319de23
User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 50532
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) »

Sorry, can't help you. All you can do is turn off VistaDelete (VistaDelete=0 in wincmd.ini). Maybe you have some third party trash can installed which doesn't like that function.
Author of Total Commander
https://www.ghisler.com
Post Reply