We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In Fuchsia, we're doing an update of our vendored version of crossbeam. As part of it, we found some uses of alloc::alloc that may be incorrect, like https://github.com/crossbeam-rs/crossbeam/blob/master/crossbeam-epoch/src/atomic.rs#L254. According to the documentation for GlobalAlloc, it's possible for allocation to return a null pointer in two cases:
alloc::alloc
This risks undefined behavior if these conditions are met.
The text was updated successfully, but these errors were encountered:
Thanks! I filed #690 to fix this.
Sorry, something went wrong.
93dce5a
The fix is released in crossbeam-epoch 0.9.4.
Successfully merging a pull request may close this issue.
In Fuchsia, we're doing an update of our vendored version of crossbeam. As part of it, we found some uses of
alloc::alloc
that may be incorrect, like https://github.com/crossbeam-rs/crossbeam/blob/master/crossbeam-epoch/src/atomic.rs#L254. According to the documentation for GlobalAlloc, it's possible for allocation to return a null pointer in two cases:This risks undefined behavior if these conditions are met.
The text was updated successfully, but these errors were encountered: