Closed T1MOXA closed 6 years ago
I take it this is due to lack of RAM ?
free -m
total used free shared buff/cache available
Mem: 958 733 14 1 210 159
Swap: 511 225 286
Sorry, I was never notified about this issue :flushed: Did the trick to use a lower compression level worked out?
Yes, with less compression there are no problems. But I just increased the amount of RAM, for the server is enough but for compression is not :)
Alright, great to hear
free -m total used free shared buff/cache available Mem: 958 733 14 1 210 159 Swap: 511 225 286
This way of freeing up the memory worked for me :rocket:
I was getting "can't allocate required memory" error in 7za command line tool in Windows 64bit and the solution was to use the 7zip 64bit installer and use the same command using the installed 7z.exe.
I guess 7za command line tool is 32bit and the file that I was trying to compress was 150GB which is too big and 7zip was trying to allocate more memory than 32bit supports.
I was getting "can't allocate required memory" error in 7za command line tool in Windows 64bit and the solution was to use the 7zip 64bit installer and use the same command using the installed 7z.exe.
I guess 7za command line tool is 32bit and the file that I was trying to compress was 150GB which is too big and 7zip was trying to allocate more memory than 32bit supports.
Just want to confirm that this fixed the issue for me as well.
For me this worked: reducing the number of working threads: add -mmt2 or -mmt4
Found this bug after some googling. Our issue was the same error but we got it while extracting and archive by running a self-extracting zip created with 7za v19.0. The extractor was started by a non-interactive instance of powershell (v5.1), and the issue was the prompt to overwrite existing files mixed with a non-interactive shell. Providing the -y switch to the extractor fixed the error in this case.
Оn one of the servers there was a problem.
Maybe you know what the problem is ?