-
Notifications
You must be signed in to change notification settings - Fork 23
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
libc++abi: terminating due to uncaught exception of type std::bad_any_cast: bad any cast #59
Comments
Hi @btc, it means there's an issue with the bindings, but haven't been able to narrow it down. What OS and full version of Ruby are you on? |
macOS Sonoma 14.4.1
I'm happy to collect more diagnostic information when I encounter this type of crash again. |
Thanks. The thread backtrace from Crash Reports would be most helpful. |
I've run into this error as well, so far only in specs running in our CI, but I was able to recreate it, and capture and log the core dump using logbt. Gem info:
The code was running in a Docker container from an image based on the |
@cfranklin11 Thanks for sharing. Unfortunately, I'm still having trouble finding the exact issue. I was also able to get a crash report locally, but it's for a different spot.
|
I've been looking into this off and on as time permits in order to send you a minimal reproducible example, but I've gotten stuck. Every time I try to simplify some of the code from my work codebase, it fails to trigger the For anyone else who runs into this error, I was able to narrow down the cause to be, at least in part, due to having the |
@btc and @cfranklin11 What Just found and fixed a memory issue in |
I'm using a |
I see this error on occasion. e.g. here
I'm wondering if you have an idea of what causes it? It's not a big deal, as a retry usually addresses the issue. Yet, I'm curious.
Thanks again for creating this wrapper. We are making good use of it.
The text was updated successfully, but these errors were encountered: