TotalCmd 32bit and WinRAR 7.00: problem with 4GB "Out of memory!"
Moderators: Hacker, petermad, Stefan2, white
TotalCmd 32bit and WinRAR 7.00: problem with 4GB "Out of memory!"
I start using the new WinRAR 7.00 with dictionary size of 2GB and 4GB. The TotalCmd 32bit (v11.03) have problems opening (unpacking) files inside those archives: "Out of memory!" error (the 64bit version of TotalCmd works). There's a workaround because I prefer to use the 32 bit version of TotalCmd (I've a lot of old plugins configured). What's seems strange to me is that I'm not exceeding the 4GB 32bit RAM limit (same error on 2GB dictionary size). Thanks.
Re: TotalCmd 32bit and WinRAR 7.00
TC ships an unrar.dll which might need to be updated for the new features to work properly.
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64
Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
Re: TotalCmd 32bit and WinRAR 7.00
I replaced the unrar.dll (inside the TotalCmd directory) with the new "unrar.dll" (also tried also the "unrar64.dll") downloaded from the rarlabs website. But the behavior is the same.
Re: TotalCmd 32bit and WinRAR 7.00
You don't have 4GB Ram on an x86 application.EXECUT0R wrote: 2024-03-16, 16:18 UTC I start using the new WinRAR 7.00 with dictionary size of 2GB and 4GB. The TotalCmd 32bit (v11.03) have problems opening (unpacking) files inside those archives: "Out of memory!" error (the 64bit version of TotalCmd works). There's a workaround because I prefer to use the 32 bit version of TotalCmd (I've a lot of old plugins configured). What's seems strange to me is that I'm not exceeding the 4GB 32bit RAM limit (same error on 2GB dictionary size). Thanks.
Windows 11 Home, Version 24H2 (OS Build 26100.3915)
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
Re: TotalCmd 32bit and WinRAR 7.00
How much memory an x86 excutable can use on a 64bit OS?
For x86 executable on x64 machine it consumes by default 2GB; if "IMAGE_FILE_LARGE_ADDRESS_AWARE" is set it can use 4GB.
(MSDN)
I'll assume "TotalCmd.exe" doesn't support "IMAGE_FILE_LARGE_ADDRESS_AWARE" extension.
Thanks.
For x86 executable on x64 machine it consumes by default 2GB; if "IMAGE_FILE_LARGE_ADDRESS_AWARE" is set it can use 4GB.
(MSDN)
I'll assume "TotalCmd.exe" doesn't support "IMAGE_FILE_LARGE_ADDRESS_AWARE" extension.
Thanks.
Re: TotalCmd 32bit and WinRAR 7.00
EXECUT0R,
Dictionary size is not equal to RAM usage. From WinRAR Help:What's seems strange to me is that I'm not exceeding the 4GB 32bit RAM limit (same error on 2GB dictionary size).
RomanCompression memory requirements vary depending on the dictionary size, such as about 7x of dictionary size for 1 GB and 1.5x for 64 GB dictionary. Decompression needs slightly more memory than a single dictionary size.
Mal angenommen, du drückst Strg+F, wählst die FTP-Verbindung (mit gespeichertem Passwort), klickst aber nicht auf Verbinden, sondern fällst tot um.
Re: TotalCmd 32bit and WinRAR 7.00
Thanks a lot Hacker this explain very well the problem.
Re: TotalCmd 32bit and WinRAR 7.00: problem with 4GB "Out of memory!"
2EXECUT0R
If you install the combined 32/64 Bit TC
the x86 plugins are only one button press away.
If you install the combined 32/64 Bit TC
the x86 plugins are only one button press away.
Windows 11 Home, Version 24H2 (OS Build 26100.3915)
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
Re: TotalCmd 32bit and WinRAR 7.00: problem with 4GB "Out of memory!"
Thanks Horst.Epp I'll try.
Re: TotalCmd 32bit and WinRAR 7.00: problem with 4GB "Out of memory!"
For those interested I've bypassed (not solved) the problem simply unchecking "Configuration > Packer > RAR > Use internal un-RAR if possible".
Naturally there are drawbacks, if you choose a file to unpack you've to wait and it's not possible use TotalCmd till the process complete.
Naturally there are drawbacks, if you choose a file to unpack you've to wait and it's not possible use TotalCmd till the process complete.