PureJavaSnappy is not thread-safe #270
Comments
bokken
pushed a commit
to bokken/snappy-java
that referenced
this issue
Dec 2, 2020
xerial
pushed a commit
that referenced
this issue
Jan 20, 2021
#270 Co-authored-by: BO8979 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
Snappyclass maintains a single static instance ofSnappyApi[1].PureJavaSnappyhas atablemember variable[2], which is mutated during compression operations[3,4,5,6].Concurrent compression calls seem likely to corrupt each other.
[1] - https://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/Snappy.java#L52
[2] - https://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/pure/PureJavaSnappy.java#L16
[3] - https://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/pure/PureJavaSnappy.java#L86
[4] - https://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/pure/PureJavaSnappy.java#L102
[5] - https://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/pure/SnappyRawCompressor.java#L119
[6] - https://github.com/xerial/snappy-java/blob/master/src/main/java/org/xerial/snappy/pure/SnappyRawCompressor.java#L172
The text was updated successfully, but these errors were encountered: