Kills Total Commander process when trying to modify 7z-SFX archive via CTRL+PGDN

[GodOrochi]

Create 7z SFX archive.
Try do delete a file after entering exe archive via CTRL+PG DOWN
Using latest Total Commander 11.51 x64.
Latest 7-Zip ZS 24.09 - v1.5.7 - Release 1.

[sebres]

1. Which compression method? Or doesn't it matter?
2. Only in SFX-archive (not in .7z)?
3. Only in Total Commander (not in 7-zip FM)?

[ZenLiuCN]

just meet same problem:
TC version: 11.51
7z version: 1.5.7 for 24.09
Action: modify 7z contents
Result: TC crash
Compression Method: tested in zstd and lzma2, lzma2 will should progress dialog before crash, and zstd not show.
Not in FM: yes

[ZenLiuCN]

an windows error log may help:

  <Data Name="AppName">TOTALCMD64.EXE</Data> 
  <Data Name="AppVersion">11.51.0.0</Data> 
  <Data Name="AppTimeStamp">00000000</Data> 
  <Data Name="ModuleName">tcbit7z64.dll</Data> 
  <Data Name="ModuleVersion">0.0.0.0</Data> 
  <Data Name="ModuleTimeStamp">67598d3e</Data> 
  <Data Name="ExceptionCode">c0000005</Data> 
  <Data Name="FaultingOffset">0000000000013741</Data> 

maybe tcbit7z64.dll should do some patch?

[ZenLiuCN]

just check: as tcbit7z64.dll is closed source dll ship with TC . current only way is use config->7-zip then point to a 7zG.exe.

[sebres]

maybe tcbit7z64.dll should do some patch?

It is almost obvious... But I cannot say what exactly may cause that, because 7zip (whether ZS or stock mainline version) and its interfaces got hugely updated in the last time. I guess something between 22.01 and 24.09.
Since the interfaces affected too, it could be enough to recompile the TC-binding, however I cannot exclude the necessity to adjust it if compilation would fail, since the headers may be not compatible anymore.

[ZenLiuCN]

tcbit7z64 export 4 functions:

1. delete7zFiles2
2. get7zSupportedMethods
3. pack7zFiles
4. rename7zFile2
   IF those function signatures are known. Maybe just another replaced wrapper could be done.
   Otherwise. to configure use executeable to process 7z file modification with zstd should be only way for now.

[sebres]

That exports are for TC itself, the implementation of binding to 7zip is fully internal.
With other words the answer is - no. Neither they are known, nor they can be "wrapped" somehow (with manageable and justified effort).
Basically the issue is wrong here (I see it as completely 3rd party issue) and shall be rather opened on TC side.

[ZenLiuCN]

I full agree this can be closed or mark as Question. Thanks for your help. The issue should belongs to TotalCommander itself.

[sebres]

Just for the record, thinking twice, I could also imagine that it could be the fix for #401 and #353, just... they are not released yet.
The question is which 7zip version exactly TC uses (or compiled against), and whether one could bisect (or try some older releases) in order to find the causation commit.

And however tcbit7z64.dll doesn't tell me something, but we seem to build and release TotalCmd (part of its plugin?) that contains tc7z64.dll (without bit)... So my first question would be are they the same thing and if yes, can someone probably test another version (of it and related 7z.dll)?