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

Potential data race when using CompressionPolicy::High with Freelist::Optimistic or Freelist::Pessimistic #36

Open
al8n opened this issue Sep 23, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@al8n
Copy link
Owner

al8n commented Sep 23, 2024

cargo miri reports data race when using CompressionPolicy::High with Freelist::Optimistic or Freelist::Pessimistic and a reclaim happens in the CAS error branch, not sure if the data race happens because of this crate or the rarena_allocator crate.

Only allow users to customize CompressionPolicy and Freelist when the experimental feature of this crate is enabled for a temporary solution.

@al8n al8n added the bug Something isn't working label Sep 23, 2024
@al8n al8n self-assigned this Sep 23, 2024
@al8n al8n changed the title Potential data race when enable CompressionPolicy::High Potential data race when CAS fails and the underlying allocator try to reclaim memory Sep 23, 2024
@al8n al8n changed the title Potential data race when CAS fails and the underlying allocator try to reclaim memory Potential data race when using CompressionPolicy::High with Freelist::Optimistic or Freelist::Pessimistic Sep 24, 2024
@al8n
Copy link
Owner Author

al8n commented Sep 25, 2024

Seems that the data race was caused only by the CompressionPolicy::High is enabled, see #38.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant