-
Notifications
You must be signed in to change notification settings - Fork 15.6k
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: segfault on Apple Silicon (M1/M2) Macs #13355
Comments
To debug an issue like this, we need a repro. Does simply importing pg_query in an empty app trigger the crash? If not, how much of your app can you delete and still get the crash? I recommend trying this on a branch. Try deleting things until you have the smallest amount of code that still triggers the crash. |
Yeah, I guess. Actually, there is no code using the gem in the app, just the gem in the Gemfile. |
On my M1 mac, I tried the following:
This did not reproduce the crash. So it appears that merely importing pg_query is not enough to reproduce this issue. So we still need a repro before we can debug this. |
I'm running it in Docker (Alpine 3.16) which probably results in using different architecture ( |
It could be that, or it could be a hundred other things about your setup. The only way to find out is to reduce the crash until you have a minimal repro. There are some tips for creating a minimal repro here: https://stackoverflow.com/help/minimal-reproducible-example |
Actually, now that you mention it, I don't think our binary gems are compatible with Alpine, see: #12904 (comment) That comment also contains workarounds for this. |
I see. Thanks, I missed that issue. |
What version of protobuf and what language are you using?
Version: 3.24.0.rc.2
Language: Ruby
What operating system (Linux, Windows, ...) and version?
macOS Ventura 13.4 (22F66)
What did you do?
I'm using pg_query gem which has protobuf as depedency.
Log
Might be (somehow) related to #11968.
The text was updated successfully, but these errors were encountered: