fullstaq-ruby / fullstaq-ruby/server-edition

Segmentation fault with ruby 3.3-jemalloc

Open
#155 3 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Shell
Stars
630
Forks
38
PR merge metrics
No merged PRs in 30d

Description

**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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.