Closed levkk closed 5 months ago
Downgrading back to 0.24 fixed the segfault.
Hi, thank you for reporting this. Hmm, it is strange the snippet runs into a segfault with the latest aws_sdk_ec2
.
Can you run any of the ec2 examples without the segfault? I'm trying to see whether the segfault is specific to the run_instances
operation or it occurs with any operation in aws_sdk_ec2
.
What Rust version is this? Anything else weird about your environment? Are you spawning a thread with a reduced stack size?
25 stack frames is not a lot...
Is it possible to see the size of each frame with GDB?
I'm thinking now I might be a victim of a small stack here. Tokio by default allocates 2MB per thread and my app is getting pretty hefty. Not sure why the SDK upgrade triggered the stack overflow, maybe it added a few more levels of abstraction and that finally tipped the stack size over. In any case, I increased my stack size to 4MB and I'm not seeing this issue anymore.
I'll reopen this issue if the stack size fix doesn't end up working long term.
Thank you.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
I've been getting a lot of stack overflow errors inside smithy after upgrading to latest version. I was on 0.24 before. Backtrace below:
Backtrace
Platform
Tested and reproduced on Mac OS (Apple M1 Max, Ventura) and Ubuntu 22.04 (AMD).
Expected Behavior
Not to segfault in a supposedly memory-safe language.
Current Behavior
I'm getting a segfault.
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
Version
Environment details (OS name and version, etc.)
Mac OS Ventura M1 (also reproduced on Ubuntu 22.04 AMD)
Logs