TC 11.00 [Lister] Endless Crashes...

[tcmuppet]

Recently updated to v11.0 and since then experiencing a huuuge number of crashes while working with Lister.

The very same setup (same plugins etc, ) under TC10.x worked like a charm, no issues.

I work with a lot of files, so use Lister constantly and in over 20 years of experience with TC never seen the program crashing so often. Since there is no dialog box with the crash info I may need to run TC under xdbg to see if I can see where the exception happens.

Curious if anyone else is experiencing it.

[white]

Since there is no dialog box with the crash info I may need to run TC under xdbg to see if I can see where the exception happens.

Perhaps you can find info about the crashes in the Windows Reliability History.

[tcmuppet]

thanks, good call, but all the records show RIP as ... 0x0

Code: Select all

Faulting application name: TOTALCMD64.EXE, version: 11.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x38f4
Faulting application start time: <timestamp>
Faulting application path: TOTALCMD64.EXE
Faulting module path: unknown
Report Id: <GUID>
Faulting package full name: 
Faulting package-relative application ID:

[white]

Probably an Access Violation error of a plugin. Any idea what kind of files you were viewing and the Lister plugins involved in that?

[tcmuppet]

I work a lot with malware samples, so do a lot of ALT+F7 searches, then quickly viewing file contents after ALT+L and then going in and out quite quickly with F3/ESC, also, sometimes changing to Unicode view to search for strings (btw. this is a nice one feature request there to search Unicode strings natively w/o a need to change codepage), and this is when I observed the largest number of crashes -- it's like during the Unicode view rendering something is not rendering it fast enough and keyboard input during this process causes TC to crash

I will run under xdbg to see if it is a plug-in (highly possible)

thx!

[ChristianGruen]

A problem with CudaLister crashed my TC instance. This is what the Windows Reliability History says for me (Zuverlässigkeitsverlauf, in German):

Code: Select all

Problemereignisame:	APPCRASH
Anwendungsname:	TOTALCMD64.EXE
Anwendungsversion:	11.0.0.0
Anwendungszeitstempel:	00000000
Fehlermodulname:	cudalister.wlx64
Fehlermodulversion:	0.0.0.0
Fehlermodulzeitstempel:	00000000
Ausnahmecode:	c0000005
Ausnahmeoffset:	0000000000198d6a
Betriebsystemversion:	10.0.22621.2.0.0.256.48
Gebietsschema-ID:	1031
Zusatzinformation 1:	fc16
Zusatzinformation 2:	fc16d7a7bb3794a206082c2402ef7fb9
Zusatzinformation 3:	3b36
Zusatzinformation 4:	3b369723cda3165039d608928fa55169

[Horst.Epp]

What's your CudaLister version ?
Actual is 1.8.1.0

[ChristianGruen]

I also use 1.8.1.0.

[ghisler(Author)]

2tcmuppet
Do you use any plugins? If yes, you can try viewing the file with Alt+Shift+F3 without plugins and then switch through them via "Plugins" menu to find the culprit. Or you can create a crash dump like this:

0. Get procdump from 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)
in Total Commander with Ctrl+Shift+F5, e.g. procdump.lnk
3. Open the properties of 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 file from c:\dumps.

Alternatively, you can analyze the crash dump yourself as follows:
0. Get Windbg from Microsoft:
https://developer.microsoft.com/en-us/windows/hardware/download-windbg
1. Create new directory c:\Symbols
2. Run Windbg
3. File - Symbol search path, add the following:
srv*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
4. File - Open crash dump - choose the dmp file
5. Enter the following in the command line:
!analyze -v
(including the exclamation mark!) and press ENTER.
6. Wait
7. When the result is there, select all, press Ctrl+C and paste the result to the email body, or post it here.

[Rekrul]

For what it's worth, I've been using the 32-bit version of TC11.00 for a while now and I've only had Lister crash on me once when I went to close it. At the time I was just viewing a plain text file.

[ghisler(Author)]

There are plain text plugins too like the above mentioned CudaLister.

[gdpr deleted 6]

There are plain text plugins too like the above mentioned CudaLister.

Don't use the current version 1.8.1.0 of CudaLister. It has a severe bug that can destroy/overwrite arbitrary files depending on your search and text selection behavior in CudaLister: https://github.com/Alexey-T/CudaLister/issues/112

UPDATE: 1.8.2.0 of CudaLister has been released which fixes the severe bug in 1.8.1.0 regarding uncommanded overwriting of arbitrary files. I strongly recommend that any user of 1.8.1.0 updates to 1.8.2.0 as soon as possible. CudaLister 1.8.2.0 can be downloaded from the project's github site: https://github.com/Alexey-T/CudaLister/releases/tag/1.8.2.0