[TC 11.50ß2] crashes after trying to create a copy of a file in a folder with a long path

[sklart]

1. I'm trying to create a copy of a file in the current folder in Total Commander using Ctrl+C, Ctrl+V.
The path to the file exceeds the standard Windows restrictions, but this suits me because in Total Commander I can work with paths like this.
2. The system message "1 action interrupted" appears with text "The source and destination file names are the same" (these window title and text are in Russian, I have given them in English for simplicity). Usually, in this case, a file is created next to it with the note “— копия” ("— copy" in Russian)
3. I close this window. After a certain time Total closes. This program crash does not always happen with this sequence of this actions, but in an hour of my work there were already two closures.

The file paths (for example) are as follows (with Cyrillic characters)
d:\Documents\YandexDisk-osmet.rusclad\Объекты\Строительство ПС 110 кВ Кага\ИД\Площадные объекты\+П456_2023-Р-ЭС.5, том 5 (ТП-5 Очистные сооружения. Электротехнические решения)\Том целиком\П456_2023-Р-ЭС.5, том 5 (Электротехнические решения. ТП-5 Очистные сооружения).pdf

Spoiler

Code: Select all

Имя сбойного приложения: TOTALCMD64.EXE, версия: 11.50.0.0, метка времени: 0x00000000
Имя сбойного модуля: DUI70.dll, версия: 10.0.26100.1882, метка времени: 0x60f1ff7e
Код исключения: 0xc0000005
Смещение ошибки: 0x00000000000428d7
Идентификатор сбойного процесса: 0xBC4
Время запуска сбойного приложения: 0x1DB218D13A9F963
Путь сбойного приложения: C:\Program Files (x86)\Total Commander\TOTALCMD64.EXE
Путь сбойного модуля: C:\WINDOWS\SYSTEM32\DUI70.dll
Идентификатор отчета: 1868ba0d-9b41-47df-bfb3-49189d780547
Полное имя сбойного пакета: 
Код приложения, связанного со сбойным пакетом: 

Archives with memory dumps and an event file available via https://drive.google.com/drive/folders/1an11GSZP-UAuDpLbhEvL4VBfC7snLeJb?usp=drive_link.

Thanks!

[petermad]

If you use Ctrl+C -> tCrl+V to copy, the copying is done by Windows not by TC, so I guess that is why you get the error message, because Windows does not support long paths as TC does.

Hat happen if you use Shift+F5 co make a copy in the same folder?

[white]

Poor Windows having to deal with this
I created a 0 byte file with that path and tried it. When I click Skip, it shows a progress bar while copying the file to .. itself I guess It takes relatively long to skip copying by copying a 0 byte file to itself, but apparently it succeeds

No crash as of yet.

[white]

2petermad
I think the issue is not that Windows fails, but that it causes TC to crash.

[petermad]

2petermad
I think the issue is not that Windows fails, but that it causes TC to crash.

`
Right, but is it even possible for TC to check the path length when the user presses Ctrl+C ?

[tuska]

Perhaps this setting will help?
How to Make Windows 10 Accept File Paths Over 260 Characters

regedit.exe (Admin)
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem > LongPathsEnabled 1 Hexadecimal

[sklart]

If you use Ctrl+C -> tCrl+V to copy, the copying is done by Windows not by TC, so I guess that is why you get the error message, because Windows does not support long paths as TC does.

That’s what I’m also writing about, that earlier, despite all the windows warnings, in TC everything worked fine

2petermad
I think the issue is not that Windows fails, but that it causes TC to crash.

Exactly like that!

Perhaps this setting will help?
regedit.exe (Admin)
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem > LongPathsEnabled 1 Hexadecimal

This registry key has long been set to this value

[ghisler(Author)]

No crash here on Windows 11, the file is copied just fine.

[white]

No crash here on Windows 11, the file is copied just fine.

I don't have experienced a crash either, but I can't copy the file using Ctrl+C, Ctrl+V (also using Windows 11).

Note that the report says that the crash happens later, not directly after trying to copy the file. Perhaps it is related to the new Windows 24H2 version that the topic starter uses.

[Horst.Epp]

For me, bug not confirmed
I'm on Windows 11 24H2
I created exactly that scenario.
There is no problem to copy and paste this file name from the long path
to any other local path.

[white]

For me, bug not confirmed
I'm on Windows 11 24H2
I created exactly that scenario.
There is no problem to copy and paste this file name from the long path
to any other local path.

The scenario is not pasting the file to any other local path. It's about pasting it to the same path as the source file.

[Horst.Epp]

The scenario is not pasting the file to any other local path. It's about pasting it to the same path as the source file.

This also makes no problem here.

[ghisler(Author)]

Maybe it's caused by an Explorer extension which can't handle the long name? Try finding it with ShellExView (search for it here in the forum).

[ghisler(Author)]

Moderator message from: ghisler(Author) » 2024-10-29, 09:46 UTC

Moved to will not be changed