You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Run command 'bin/rails db:setup'
I'm sorry I can't give you more details, how could I gather more information? Thank you
The text was updated successfully, but these errors were encountered:
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:
I'm sorry I can't give you more details, how could I gather more information? Thank you
The text was updated successfully, but these errors were encountered: