heroku-buildpack-jemalloc icon indicating copy to clipboard operation
heroku-buildpack-jemalloc copied to clipboard

Heroku buildpack with jemalloc

Results 8 heroku-buildpack-jemalloc issues
Sort by recently updated
recently updated
newest added

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

Came here after reading https://www.speedshop.co/2017/12/04/malloc-doubles-ruby-memory.html ``` Using Ruby version: ruby-2.4.2 ERROR: ld.so: object '/app/vendor/jemalloc/lib/libjemalloc.so.1' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ``` This is after `heroku...

I am investing using this buildpack. Durning my deployment to heroku, the build is rejected do to an error (cannot open shared object file). Some of the output (same error...

bug

I have: ``` $ heroku buildpacks 1. https://github.com/heroku/heroku-buildpack-apt 2. https://github.com/mojodna/heroku-buildpack-jemalloc.git#v3.6.0 3. heroku/ruby ``` When I deploy, the build phase crashes: ``` [...] remote: -----> jemalloc app detected remote: -----> Vendoring...

bug

Originally from @brian-kephart @nateberkopec: I'll leave this for you to merge and make live (but I'll create the release w/ a new binary).

Not sure if we actually need to change anything for this or not

Example: ``` $ tcmalloc puma Injecting tcmalloc... ``` It would just help with debugging as a bit of an "idiot test".