Skip to content

events: work around the bug in concurrent-queue #2444

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

Closed
wants to merge 1 commit into from

Conversation

link2xt
Copy link
Collaborator

@link2xt link2xt commented May 13, 2021

Use power of 2 channel capacity to avoid occasional out of bounds access panic.

Address #2442

@link2xt link2xt force-pushed the concurrent-queue-workaround branch from 22b6090 to 1f77305 Compare May 13, 2021 22:38
@link2xt
Copy link
Collaborator Author

link2xt commented May 13, 2021

Upstream bugreport: smol-rs/concurrent-queue#11

Copy link
Contributor

@r10s r10s left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. that was probably a hard to find and unexpected issue :)

@link2xt link2xt marked this pull request as draft May 15, 2021 00:55
@link2xt
Copy link
Collaborator Author

link2xt commented May 15, 2021

After checking the source code, I doubt there is a bug. I suspect a hardware problem, suggest @Simon-Laux to run memtest. I don't see any code path that can result in out of bounds access.

Use power of 2 channel capacity to avoid occasional out of bounds access panic.
@link2xt link2xt force-pushed the concurrent-queue-workaround branch from 1f77305 to 9635fb3 Compare May 16, 2021 13:33
@Simon-Laux
Copy link
Contributor

memtest passed without any errors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants