-
Notifications
You must be signed in to change notification settings - Fork 48
Stack overflow when updating from 1.5.1 to 1.5.3 #53
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
Comments
Update: it's a little easier to reproduce in that it doesn't actually need a mongodb deployment. Running
triggers the behavior without needing a test instance. |
No time to check this at the moment. My best guess is that some function is calling itself recursively, as this crate shouldn't use that much stack space. Do you have more information on where, exactly, this stack overflow occurs? Knowing the conditions that cause this would go a long way towards figuring out what was added that went wrong. |
There's no recursion involved, and it's worth noting that the same test runs under tokio with no issues. Where exactly the error happens depends on the presence of debugging statements; without them, the lldb stacktrace is below.
|
Interestingly |
It seems like |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
In that case, it is unlikely to be related to this issue (stack overflow). I've opened a #57 to track the issue you are encountering. |
This was added in #37 as an optimization, but has since lead to many bugs. See the issues #53, #57 and #60 for more information. I do not have the bandwidth to address all of these bugs, so I'm taking the path of least resistance by just removing the problematic code. CLoses #53, #57 and #60 Signed-off-by: John Nunley <[email protected]>
This was added in #37 as an optimization, but has since lead to many bugs. See the issues #53, #57 and #60 for more information. I do not have the bandwidth to address all of these bugs, so I'm taking the path of least resistance by just removing the problematic code. CLoses #53, #57 and #60 Signed-off-by: John Nunley <[email protected]>
A specific test has started failing with a stack overflow in the Rust mongodb driver when using
async-std
without any code change on our part; I've narrowed down that this happens when the dependency tree includesasync-executor
1.5.3, but not when it's pinned to 1.5.1. This can be reproduced by running this test against a replica set topology:Unfortunately, I haven't had much success constructing a minimal reproduction - I strongly suspect some badly-behaved
unsafe
code is at the root of this, since changes that affect memory layout (unrelated struct fields) have caused this behavior to unpredictably fail to occur. Let me know if there's more information I can provide that would be useful!The text was updated successfully, but these errors were encountered: