Closed mrthan closed 10 years ago
Hi there,
Thanks for letting us know – seems like an issue with yajl
. Can you either try to install the oj
gem for a faster JSON parser, or remove yajl
to test if that does it?
Thanks!
Thanks, I installed oj
and oj_mimic_json
but the error still occurred. Tried checking for a toolbelt update and updated from 3.5 to 3.6, the fork
is successful on 3.6.
Is a global install of those gems the way to affect the heroku use of them?
Ah, good to hear! We tried to introduce multi_json
with 3.5 but reverted because of issues in some environments.
The client defaults to a pure-ruby parser, but might use others when available for better performance. In this case it seems like it picked yajl
from your system. Are you using that gem elsewhere/does it seem to work?
Initially logged with Heroku support, appears to be an issue when RVM ruby is installed on a dev machine: https://help.heroku.com/tickets/113492
I'm trying to heroku fork a RoR application. Toolbelt creates the newinstance OK but core dumps during the database transfer, details below.
Running on Lubuntu, Heroku Toolbelt version is 3.5.0 (i686-linux) ruby/1.9.3 I tried with system ruby at 1.9.3, ditched that leaving 2.0.0 and still the same. I can manually copy the database to workaround this, but I'm unsure exactly what I can do with Fork as it stands.
Creating fork my-manager-dev... done Copying slug... done Adding papertrail:choklad... done Adding pgbackups:plus... done Adding heroku-postgresql:dev... done Transferring database (this can take some time)... /usr/local/heroku/vendor/gems/multi_json-1.8.4/lib/multi_json/adapters/yajl.rb:11: [BUG] Segmentation fault ruby 1.9.3p194 (2012-04-20 revision 35410) [i686-linux]