Skip to content
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

Segmentation fault with ruby 3.3-jemalloc #155

Open
diasjorge opened this issue Oct 2, 2024 · 0 comments
Open

Segmentation fault with ruby 3.3-jemalloc #155

diasjorge opened this issue Oct 2, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@diasjorge
Copy link

Describe the bug
While testing the upgrade for one of our applications to ruby 3.3 we are consistently getting segmentation fault errors when running on our CI systems (github actions self hosted k8s runners).
We tested changing to not use jemalloc and the problem disappeared.
Is this the right repository to report this bug?
I haven't been able to reproduce this outside that environment.
Any recommendations so we can find the root cause? The error said "Segmentation Fault (core dumped)" but I wasn't able to find the core dump anywhere on the system.

To Reproduce
Linux distribution: ubuntu 24.04 container inside github actions.
Package name: fullstaq-ruby-3.3-jemalloc

Steps to reproduce the behavior:

  1. Run command 'bin/rails db:setup'

I'm sorry I can't give you more details, how could I gather more information? Thank you

@diasjorge diasjorge added the bug Something isn't working label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant