-
Notifications
You must be signed in to change notification settings - Fork 93
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 (core dumped) for Ruby <3.1.0 using jemalloc (--with-jemalloc) #242
Comments
I don't have more than this in the console output of this simple test:
I tried running some
I believe there's some incompatibility with ruby 3 here. I ran the other tests you talked about though (2.7.5 and 2.6.9) on x86:
→ I could not compile the gem here, I didn't dive deeper.
So the problem is present here too. I tried some gdbdump there too but without success (I can't get the core dump file to be created)
I also tried running ruby in GDB directly and managed to get this if it's of any help:
|
Ruby: 3.0.2 how to fix this issue?
|
I don't see how your issue is related to this one, @oLeVanNghia. This is about using jemalloc resulting in a segmentation fault. |
Encountered the same issue
Prerequisites:
Installing |
I just compiled Ruby 3.0.6 with jemalloc on macOS Venture 13.4 via rvm:
…and it works 🥳
|
Extracted from #193 (comment) (thanks @jarthod 🙇).
Using Ruby build with
--with-jemalloc
seem to cause a segmentation fault with Ruby < 3.1.0, tested with latestmini_racer
(0.6.3) andlibv8-node
(16.10.0.0). UsingLD_PRELOAD
seems to work fine for Ruby 3.0.3 and 3.1.0.See #193 (comment) for testing Ruby 3.1.0 and 3.0.3 with
--jemalloc
onx86_64-linux
(@jarthod: Do you have some more information you can provide on the crash? output? logs?).The issue can be triggered by:
I'll follow up (and update) with more tests on different Ruby versions (2.6.9 and 2.7.5) and architectures (x86 and aarch).
Update: Works with (build with
--with-jemalloc
, tested with https://github.com/moritzheiber/ruby-jemalloc-docker/pkgs/container/ruby-jemalloc):The text was updated successfully, but these errors were encountered: