-
Notifications
You must be signed in to change notification settings - Fork 113
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
Errors with LD_PRELOAD version #20
Comments
I'm not sure jemalloc is supposed to showup in RbConfig::Config['LIBS']. Somebody asked me about this before, "how do I know if Jemalloc is actually being used when using LD_PRELOAD", and I don't think there's a great solution. |
I had a feeling you were going to say that. As for the other errors, I guess these never got resolved? |
@gbatterbee To see if jemalloc is enabled you can use the trick mentioned in this comment: gaffneyc#5 (comment) If you're having trouble getting it set up I would recommend taking a look at my fork which should be easier to get started with. |
Ah, nice, thanks - I'll take a look. |
Hi, thanks for setting up this build pack.
I'm not sure if there is a problem or not, though I would log it here.
We're running
Ruby 2.37
Rails 4.2.0
As per docs I added Env Var
LD_PRELOAD=/app/vendor/jemalloc/lib/libjemalloc.so.1
But this errored with
If I run these in bash,
So then I checked this
And changed
LD_PRELOAD to /app/vendor/jemalloc/lib/libjemalloc.so
I then pushed a new change and got a build error.
JSON::ParserError: 784: unexpected token at 'ERROR: ld.so: object '/app/vendor/jemalloc/lib/libjemalloc.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
So I removed LD_PRELOAD and used
web: jemalloc.sh bundle exec puma -C config/puma.rb
I can push a change through, but querying
~ $ ruby -r rbconfig -e "puts RbConfig::CONFIG['LIBS']"
Gives me
-lpthread -lgmp -ldl -lcrypt -lm
So I don't know if this is what is expected or if it is working properly?
If you could confirm if this is correct, or if there is an error here?
Many thanks!
The text was updated successfully, but these errors were encountered: