Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Error, a deadly bug. #223

Closed
57382 opened this issue Aug 26, 2021 · 11 comments
Closed

New Error, a deadly bug. #223

57382 opened this issue Aug 26, 2021 · 11 comments

Comments

@57382
Copy link

57382 commented Aug 26, 2021

5GB folder, in 7-Zip ZS 21.03 - v1.5.0 - Release 1

image
image

@leo-liar
Copy link

leo-liar commented Aug 26, 2021

Yeah, I just got this too. It's independent of the size of the file/folder one wants to encrypt and the compression level. Selecting Zstandard immediately gives this error.

(Changing/removing parameters, password, etc. doesn't help either.)

Screenshot:

image

@g0blin-NN
Copy link

g0blin-NN commented Aug 26, 2021

if you choose .tar, that is also a mistake.

rolling back to version 21.02

@mcmilk
Copy link
Owner

mcmilk commented Aug 26, 2021

I will take a look at it ...

@g0blin-NN
Copy link

g0blin-NN commented Sep 4, 2021

https://sourceforge.net/p/sevenzip/discussion/45797/thread/9f5b067368/?page=2#5981

probably not that. it shows how much memory is needed. here is zero.

@forworldm
Copy link

missing code to handle zstd

return (UInt64)(Int64)-1;

@skripts-eu
Copy link

Encountered the same error. Compressing only 9 MB, in 7-Zip ZS 21.03 - v1.5.0 - Release 1 /
error (2)
OS Version 10.0.19043 Build 19043

@g0blin-NN
Copy link

As I understand it, Igor introduced a "stub". that is, if compression requires more memory than the RAM on the computer, this window pops up. and since zstandard always shows zero. "stub" / window will always be there. There are two options. or say how much memory you need, or it will roll back to the 19.00 release version with updates to zstandard up to 1.5.0. and wait for Igor to change his mind.

@forworldm
Copy link

ConvertUInt64ToString((size + (1 << 20) - 1) >> 20, temp);

actually, it's UINT64_MAX, but overflow to 0. make CCompressDialog::GetMemoryUsage_Dict_DecompMem return zero instead of (UInt64)(Int64)-1 should be able to bypass the check.

@forumber
Copy link

I got the exact problem too for every non standart codecs. (modified 7zip)

@fiveangle
Copy link

fiveangle commented Oct 4, 2021

Came to say same, but realized 21.03 was pulled from the releases. Dropping down to 21.02 resolves for now.

@mcmilk mcmilk closed this as completed in 8bb8d13 Oct 4, 2021
mcmilk added a commit that referenced this issue Oct 5, 2021
@g0blin-NN
Copy link

g0blin-NN commented Nov 18, 2021

@eladkarako won't work everywhere.

The value SegmentHeap indicates that segment heap will be used. Segment heap is a modern heap implementation that will generally reduce your overall memory usage. This element is supported in Windows 10, version 2004 (build 19041) and later. ©

1809 ltsc?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants