-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
zstd.decompress not threadsafe for shared objects #4206
Comments
This repository and its issue board focus on the underlying C reference implementation of The question you've raised appears to be specific to the To ensure a more accurate response, we recommend directing your question to the relevant repository that maintains the |
ack, thanks. is the following the appropriate/canonical zstd python repo? |
There are several Python bindings, so I can't be completely sure which one you use. |
thanks! |
Describe the bug
Hi, When I have an object zstandard.ZstdCompressor() shared across a concurrent.futures.ThreadPoolExecutor, I see some nondeterministic behavior when using this object to compress.
My expectation was that there is no shared state in calls to compressor.compress(bytes), so it was surprising to me that threadedness saw some stochasticity in outputs.
To Reproduce
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots and charts
I see 4 different behaviors: a "happy path", and 3 errors. Sometimes the code outputs the decompressed values, and sometimes it does not.
One of two errors:
Another error:
The final error I'm seeing:
Desktop (please complete the following information):
!pip install zstandard # this fetched zstandard-0.23.0-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
from a free colab kernel at colab.research.google.com
Additional context
This may be a user error, but I found it surprising nonetheless
The text was updated successfully, but these errors were encountered: