Why is this RMagick call generating a segmentation fault?

Question

I\'ve been banging my head against the wall for the better part of an hour trying to figure out what\'s going wrong here, and I\'m sure (or rather hoping) it\'s something fa

Answer 1

I solved the same error (after many trials) by moving the 'gem "pg"' line in the gemfile below the fog gem, had something to do with loading dependencies I think.

Answer 2

To expand on Matthew Savage's comment, do this:

brew install imagemagick --disable-openmp

and it starts working again. No need to edit the files. (I'm not sure if thats what he's actually saying or if he's saying remove the flag, but the above homebrew command works for me on OSX 10.6)

If you already have imagemagick installed then

brew uninstall imagemagick && brew install imagemagick --disable-openmp

brew upgrade -f no longer reinstalls, so you have to uninstall it first.)

Answer 3

I was having a very similar problem on OS X 10.6.7 running Ruby 1.9.2p180.

To expand on Ash Berlin's comment, if you are using the homebrew package manager, you need to uninstall the imagemagick package and also remove the cache as well, before it will work.

Uninstall imagemagick:

brew remove imagemagick

Delete the cache:

rm -rf `brew --cache imagemagick`

Then re-install the package with this flag:

brew install -f imagemagick --disable-openmp

Answer 4

i had a similar problem using rails 3 with carrierwave on os x 10.6 and ruby 1.9.2, also crashed in a call to read everytime an image needed to be resized. doing:

brew uninstall imagemagick
brew install imagemagick --disable-openmp

solved the problem for me.

Answer 5

UPDATE: This isn't really a true answer per se (I'm still seeing the same problem in MRI 1.9.1), but I used RVM to get my MRI 1.8.7 installation and gems up to date and tried running it, and everything works perfectly. I assume the problem is that RMagick isn't yet quite compatible with 1.9.1 yet, though the documentation does specifically mention Ruby 1.9 support.

Answer 6

Saw the same problem after upgrading ImageMagick on a Linux box. There are some more notes here. I suspect some mismatch of ImageMagick libraries and linked ruby gems (which is in agreement with all the previous comments. Check out this similar thread at rubyforge. http://rubyforge.org/forum/forum.php?thread_id=48036&forum_id=33

My solution was to dump RMagick in favor of MojoMagick - a very lean ruby API which doesn't link to ImageMagick libraries but simply uses the console binaries.

It's available here : www.misuse.org/science/2008/01/30/mojomagick-ruby-image-library-for-imagemagick/

I've built a gem and added resize to fill with crop functionality which is available on github https://github.com/bunnymatic/mojo_magick