-
Notifications
You must be signed in to change notification settings - Fork 189
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
ruby 3.3.0 -> 3.3.1 new error "machine stack overflow in critical region (fatal)" #557
Comments
possibly related to grpc/grpc#36125 |
I updated a couple of apps now to Ruby 3.2.4 and freetds v1.4.12. will let you know if I run into similar issues. |
Thanks @andyundso I pointed someone (byroot) to take a quick look at the c-code and they don't think it's related to the same grpc bug. In fact, even though this was a new error for us, we've now seen it again, though only once, since downgrading back to 3.3.0. So, it appears unlikely it's related to the Ruby 3.3.0 change, but it's definitely a failure which points here.. and unfortunately I haven't been able to reproduce on demand. My guess would be it has to do with connection handling and either 1) having the remote close the connection without and tiny_tds not handling it gracefully or 2) the remote server process died and tiny_tds did not handle it gracefully or 3) having the server sent a kill signal and it not being handled gracefully, though this seems less likely in this case. |
judging from the tests, we simulate a Toxiproxy would also support to simulate a |
Looking at it a little more, I'm wondering if the overflow may be in result.c in |
I'm not positive what this is related to, but figured I'd log an issue in case it means something to someone.
Ubuntu Linux, Heroku-20 image
Ruby 3.3.1
Tiny Tds 2.1.7
The only backtrace I have is
and it's not reproducible every time.
RbConfig::CONFIG
The text was updated successfully, but these errors were encountered: