You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
It should be noted that using the old version import "github.com/pierrec/lz4" , the sample code is able to handle multiple blocks and see entire contents.
amalone-scwx
changed the title
unable to decompress multiple blocks
unable to decompress multiple frames
Sep 13, 2021
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?
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: