T.C. 10.00 reproducible crash on Windows Server 2012R2

[karlchen]

Hello, Christian.

Sorry, but on Windows Server 2012R2, I got across a reproducible way of making T.C. 10.00 64-bit crash.

1. In the file panel the cursor has to be on the [ .. ] line (1 dir up, top line of file panel).
2. I click on the following button:

   Code: Select all

   TOTALCMD#BAR#DATA
   %COMMANDER_PATH%\Utils\NotepadPP\Notepad++.exe
   ?%S
   %COMMANDER_PATH%\Utils\NotepadPP\Notepad++.exe
   Notepad++
   
   0
   -1

3. T.C. will crash throwing this error message:

   Code: Select all

   ---------------------------
   Total Commander 10.00
   ---------------------------
   Access violation.
   Access violation
   Windows Server 2012 R2 ServerStandard 6.3 (Build 9600), base: 0400000
   
   Please report this error to the Author, with a description
   of what you were doing when this error occurred!
   
   Stack trace (x64):7E61F6
   7EA4EA A4F6D9 790F09 8AF3A0 8A3F53 43A149 99D251 8D71A0
   9A8DDB 
   Press Ctrl+C to copy this report!
   Continue execution?
   ---------------------------
   Yes   No   
   ---------------------------

Yes, it is easy to avoid the crash by paying a little bit of attention.
The same steps do not cause any problems, when executed in my favourite environment e.g.: T.C. 10.00 64-bit under Wine 4.0 on Linux Mint 19.3 64-bit.

Best regards,
Karl

[karlchen]

Workaround / Solution:

Oops, should have tried so before reporting the crash scenario.
Changed the button to look like this:

Code: Select all

TOTALCMD#BAR#DATA
%COMMANDER_PATH%\Utils\NotepadPP\Notepad++.exe
? %S
%COMMANDER_PATH%\Utils\NotepadPP\Notepad++.exe
Notepad++

0
-1

Result:
No more crash, when clicking the button, while the cursor is on the updir [ .. ] line.
What makes the difference is in the button parameter field the added space between ? and %s

[ghisler(Author)]

Thanks for your report. It's a known bug when using %S and other multi-file placeholders when nothing is selected and the cursor is standing on "..".

[ghisler(Author)]

A user has already confirmed the bugfix in TC 10.50 beta by e-mail.