?[8.50b2a] Crash while opening nested archives

[Biozynotiker]

First of all, this Crash Report ist generated by 8.50b2a,
but the Version shown in the Report ist 8.50b1.
I also can't reproduce it again.

What I have been done:

- Navigate to an UNC path \\computername\c$\tmp\
- Open an RAR5 Solid archive (press return) (rar5 archive contains several uncompressed 7zip archives)
- Open an nested 7zip archive with the internal 7z (press return again)
- Crash
- On both computer, there is no AV installed btw.



---------------------------
Total Commander 8.50b1
---------------------------
Access violation at address 748BC05C. Write of address 00000000.
Access violation at address 748BC05C. Write of address 00000000
Windows 7 SP1 6.1 (Build 7601)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
748BC05C
4474A9 447E26 425340 447E26 425340 447355
425340 445ED5 4474A9 447E26 425340 42A94E
498C6D 447E26 425340 6F4A1B 6F25CC 5C9662
5B8F24 5BAD0A 5BDF41 4E7EE8 64C7D6 448963
445ED5 4474A9 447E26 >425340 4473E7 425340
42A9FC 42AA98 6F7833
Raw:
50004A 6C005F 54005A 4D0047 44004E 4D004B
4B0046 4E004D 44004E 6F47D3 41D1C1 5C005B
4D0047 6F48CF 6B005F 650078 5C005B 4D0047
6F49EB 6ED5C0 57005A 6F25CC 41D4DE 4D0047
447E26 447E49 425340 44004E 650078 44004E
45004B 41897D 4189AE 418A64 448182 445ED5
4480F5 43728E 447437 4474A9 447E26 447E49
425340 4473E7 44004E 45004B 448143 42701C
4474A9 447E26 447E49 425340 447355 425340
44819F 44855C 4374EF 445ED5 4480F5 445ED5

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Ja Nein
---------------------------



*EDIT*:
Rebooted both Computers, tried again about 50 times, and it crashed again.
So it happend often, but it is difficult to reproduce this.


---------------------------
Total Commander 8.50b1
---------------------------
Access violation at address 746EC05C. Write of address 00000000.
Access violation at address 746EC05C. Write of address 00000000
Windows 7 SP1 6.1 (Build 7601)

Please report this error to the Author, with a description
of what you were doing when this error occurred!

Windows exception: C0000005
Stack trace:
746EC05C
6ED00F 6ED8B8 6ED00F 6ED8B8 6F4359 6F0587
6F6FAD 6F6FAD 61015F 5B8F24 5BAD0A 5BDF41
562E31 65CEFF 6597D0 64CC17 448963 445ED5
4474A9 447E26 >425340 4473E7 425340 42A9FC
42AA98 6F7833
Raw:
50004A 6C005F 54005A 4D0047 44004E 44004E
6F47D3 680062 6ED00F 6ED8B8 41CD6D 6F49EB
6ED5C0 57005A 5C005B 425340 41D4DE 5C005B
4D0047 6BB2DA 650078 5C005B 4D0047 41D259
44004E 6ED804 6ED00F 6ED8B8 44004E 41D856
41D891 6C005F 54005A 4D0047 41D54D 41D564
4187E4 4187FC 6F47D3 41DAC8 44004E 650078
6BB2DA 6F4359 6F0587 6BB348 43EA5B 43EB9A
449F8B 448461 6F6FAD 60CE5F 6F47D3 6F488F
498C90 6F6FAD 60CE5F 6F47D3 6F488F 6EDBA0

Press Ctrl+C to copy this report!
Continue execution?
---------------------------
Ja Nein
---------------------------

*EDIT 2:*

This happend also by pressing F3 inside an RAR5 archive, so this has nothing todo with nested archives. But, when TC crashes, it uses 1,4gb ram.
The RAR5 Archive is created with 1GB Dictionary, so this seems to be the same problem like the 7zip one, with dictionary over 512mb on 32bit TC.

I don't know, if RAR5 Container contains information about used dictionary like 7zip do, to show/detect a error message instead of crashing.

[ghisler(Author)]

It seems to be the same problem with the new unrar.dll - do you use an AMD processor?

Anyway, there is a new unrar.dll on www.rarlab.com which should fix that specific problem - can you try it, please?

[Biozynotiker]

It seems to be the same problem with the new unrar.dll - do you use an AMD processor?

Intel only:)
It's a Windows 7 64bit machine, running 32bit TC.

Anyway, there is a new unrar.dll on www.rarlab.com which should fix that specific problem - can you try it, please?

The newest unrar.dll crashes also. TC seems to allocated ~1,3gig ram at this moment.

[MarcinW]

It must be some other kind of problem, those problems with Unrar.dll generated STATUS_FLOAT_STACK_CHECK (C0000092), and here we have access violation (C0000005). Because here TC allocated ~1.3GB of RAM, this may be problem with allocating memory and, as a result, null pointer reference.

[ghisler(Author)]

2Biozynotiker
The problem I referred to does not occur with Intel processors, so you must be having a different problem. Unfortunately I couldn't reproduce it so far. Could you create a small (max 500k) sample archive with this problem and send it to support at ghisler dot com, please?

[Biozynotiker]

I'll try to create such small archive to produce a crash.

The archive that produces this crash, is around 100mb in size,
contains around 13gig of data, as far i can remember.
Maybe i can send you a link to it, but i must double check the content,
because it contains database/files from a medical software.

Maybe this is really a simple out of memory thing, like 7zip one, because it also uses 1GB dictionary.

[Biozynotiker]

Ok, i managed to create such archive, but it's ~32mb in size.

Link: rar5_solid_1gb_blake2_test.rar

I also create this archive 2 times, with crc32 and blake2, both crashes.
So this seems really related to out of memory.
The archive attributes:
- rar 5
- solid
- 1gb dictionary
- blake2 hash

TC craches immediately while pressing f3 on first or last file inside the archive.

[ghisler(Author)]

Got the file, thanks! Indeed it seems to be an out of memory error. I will try to catch it, but it could be difficult - RAR takes away almost all the memory available to TC, and the error happens later somewhere else...

[Biozynotiker]

Idea:

With the command: rar.exe lt archive.rar >technical_list.txt
it is possible to list files, that is packed with a big dictionary.

So this information must be stored into the container.
Maybe this flag can be read by TC before some unpack action accours.

[ghisler(Author)]

I have just checked it - the error occurs within the Unrar.dll. It seems like the dll doesn't check whether the malloc function succeeds or fails, and just tries to read/write to the buffer. I will contact the rar author.

[Biozynotiker]

Can confirm, that the crashes are gone.