Total Commander

mhanor · Junior Member Joined: 07 Apr 2010 Posts: 16

I can reproduce a crash using TCMD 7.57a and 8.0 x86, under Windows 7 64 bit SP1, on a real machine and on a Virtualbox machine (same OS, clean install).

To reproduce it, create a Windows command batch file (.bat) with the following content, and execute it (please mind the access rights):

umbra · Power Member Joined: 14 Jan 2012 Posts: 666

I can confirm it (well, a sort of) in Win 7 and Win 8.
In a Win 8 virtual machine, when I tried it for the first time, tcmdx64.exe crashed and the x64 context menu contained something like "No response (timeout)!". After I restarted TC, I was no longer able to reproduce it - menu worked fine. I had to restart a computer to see it again.
In a Win 7 virtual machine, it was very similar - there was no crash report but everything else was the same.

edit: mhanor, every time I reload the page I see more info in your post. I had to find out about that rebooting on my own Sad

_________________
Windows 7 Pro x64, Windows 8 Pro x64

mhanor · Junior Member Joined: 07 Apr 2010 Posts: 16

I submitted the post before completing it, that's why you saw more info on each page refresh.

On my real PC, it doesn't seem to dissapear while the postmortem debugger (windbg) automatically starts and attaches itself to the failed process. It appears I can crash it over and over again. I'm thinking that the OS caches/adjusts something, while there's no postmortem debugger set, and the crash becomes unlikely without a system reboot.

ghisler(Author) · Posted: Wed May 30, 2012 7:53 am Post subject:

From your report it seems that you found some bug in an Explorer shell extension for this file type. Can you try the same right click on Explorer?
_________________
Author of Total Commander
http://www.ghisler.com

mhanor · Junior Member Joined: 07 Apr 2010 Posts: 16

There is no shell extension installed or file type set for this file extension name. I can reproduce the issue with a clean installation of Windows 7 SP1 64 bit. And there's no X64 menu entry when right clicking files in TCMD x64 and Explorer (which is also 64 bit).

petermad · Posted: Wed May 30, 2012 12:47 pm Post subject:

I can confirm the bug using mhanor's batch file - but ONLY when the vbox folder and it's subdirs are placed in the root - not if I place vbox in a subdir to the root. It doesn't matter whether it is in the root of a NTFS drive or a FAT32 drive.

Interestingly enough - if I go to Makefile.kmk in the file panel and right click it, there are no problems - it is only when I right click it in the search dialog.

I don't have any Windows associations of *.kmk files in the registry.
_________________
#524
Danish Total Commander Translator
Windows XP Home 32bit SP3 & Windows 7 Home Premium 64bit SP1 and Windows 8. TC 8.01 32 + 64bit

Get Extended Total Commander Menus

mhanor · Junior Member Joined: 07 Apr 2010 Posts: 16

Why do you think I put the "cd \" as the first line in the batch file? Smile

ghisler(Author) · Posted: Thu May 31, 2012 2:02 pm Post subject:

I do not have the problem here, Windows 7 x64, TC8 x32.

I guess that there are some Explorer extensions which are not file extension specific.

Try this: Open the x64 menu while holding down shift. If this works, choose "configure" and exclude all the displayed extensions. Now open the "X64" menu again without shift. Does it still crash?
_________________
Author of Total Commander
http://www.ghisler.com

petermad · Posted: Thu May 31, 2012 2:22 pm Post subject:

mhanor · Junior Member Joined: 07 Apr 2010 Posts: 16

Same here. I've disabled the extensions, it crashes when right clicking that file, in the search window, when hovering over X64 and not holding the shift key.

I can't reproduce the issue when enabling page heap for tcmdx64.exe, in Global Flags. If I enable other heap checking options, it finds this:

http://pastebin.com/xheAnnzZ

Later edit:
I assume that the crash stops when the fault tolerant heap makes the appropriate adjustments (FTH). FTH does output a msg to the debug
output.

ghisler(Author) · Posted: Sun Jun 03, 2012 9:00 am Post subject:

I'm sorry but I cannot reproduce it. Does it happen only with that extension, or only with that directory, or only that contents of the file? Or a combination of some of them?

And could you try to disable the extensions also with ShellExView?
_________________
Author of Total Commander
http://www.ghisler.com

mhanor · Junior Member Joined: 07 Apr 2010 Posts: 16

After disabling FTH, cleaning AppCompatFlags & rebooting, I'm able to reproduce the crash every time.

umbra mentioned a crash (2nd reply), that I think it wasn't related to the same setup. There are a few other threads on this forum, where some users reported crashes of tcmdx64 inside ntdll code, probably caused by the same issue.

What extensions should I disable with ShellExView? It lists only Microsoft extensions and it even warns about disabling certain of them. I've disabled them, but the OS feels the same, even after reboot, and tcmdx64 still crashes.

Maybe you should check if your OS has set up a FaultTolerantHeap flag for tcmdx64 and perhaps you should disable FTH: http://blogs.msdn.com/b/itasupport/archive/2009/10/08/come-disabilitare-il-fault-tolerant-heap.aspx
You could also try a virtual machine, maybe some installed extensions prohibit you from reproducing the problem.

It may have something to do with the length of the full path & file name, 67 characters

I can reproduce the crash with:

ghisler(Author) · Posted: Mon Jun 04, 2012 9:14 am Post subject:

umbra · Power Member Joined: 14 Jan 2012 Posts: 666

No more crashes in TC 8.01 rc1.
_________________
Windows 7 Pro x64, Windows 8 Pro x64

mhanor · Junior Member Joined: 07 Apr 2010 Posts: 16

Indeed, it seems safe now.