-
Notifications
You must be signed in to change notification settings - Fork 143
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
unable to decompress multiple frames #141
Comments
It should be noted that using the old version |
I bumped into the same issue with the v4 branch. It doesn't happen with the v2 branch of the library as @amalone-scwx mentioned. @pierrec , is it expected from now on? |
@phacops nope it is a bug. I havent had time to look into it yet. |
No problem, thanks for the answer. I'll try to investigate myself when I have time. |
Below is a code sample to demonstrate the issue. The issue happens when multiple LZ4 frames are in the data.
The multiBlockB64 string contains 186000 bytes of highly redundant data with LZ4 in 64KB independent blocks, each in it's own frame. I generated it with c++ library.
If I base64 decode it and use lz4c to decompress, it sees the entire 186000 bytes. However, the Go sample using this library will only see the first block. No errors reported.
If I change the block size on compression to 256KB, then the Go sample will see up to 256KB.
The text was updated successfully, but these errors were encountered: