Brian Kephart

I feel like I hijacked this issue. Sorry everyone! I started #966 so discussion here can stay focused on documentation. @texpert please see that issue for my opinions about Webpacker/Sprockets...

I too was unable to get LD_PRELOAD to work. Using jemalloc.sh in the Procfile did work, and reduced my overall memory usage significantly, but increased my swap memory usage. Some...

I managed to fix this problem by setting `LD_PRELOAD` in the script in /.profile.d. I think that the problem we're having is a result of having the environment variable present...

@ohaddahan Yes, you can check that the LD_PRELOAD value is correct as you described, but follow mojodna's instructions in this thread from 12/27/16 to make sure the specified file is...

I think there's an issue with the 5.0.0 binary. I tried to use the buildpack from the jemalloc-5.0.0 branch and got this message when deploying: ``` remote: -----> jemalloc app...

Filename was incorrect, missing a 'v'. The binary file is https://github.com/mojodna/heroku-buildpack-jemalloc/releases/download/v5.0.0/jemalloc-5.0.0-1.tar.gz Correcting the filename removed the build error. However, the new binary does not have the file `/app/vendor/jemalloc/lib/libjemalloc.so.1`. So, still...

Correction to the above: The file change in 5.0.0 doesn't appear to affect anyone who was using jemalloc via the Procfile script, since that refers to `jemalloc.sh` rather than `/app/vendor/jemalloc/lib/libjemalloc.so.2`....

I deployed using this branch and it works. Some notes: 1. Setting LD_PRELOAD using heroku config works now. It never worked for me before. 2. Typing ```heroku config:set LD_PRELOAD=`jemalloc-config --libdir`/libjemalloc.so.`jemalloc-config...

v5.0.0 just came out today. I'd do a PR for it, but I don't know how the build process works when building for a different environment than my local machine....

I've been using this buildpack on Heroku-16 for a couple months. It works just fine.