Robert Fletcher

Yes! I didn't realize we could run C coverage with Ruby tests.

We might want to see if we can track this with a 3rd party service like CodeClimate or Coveralls.

@robertleelittleiii RMagick version 2.1.6 is no longer supported. Are you able to upgrade to the latest version (4.2.2)? Unfortunately, we won't be able to help you debug 2.1.6.

@robertleelittleiii it's hard to know for sure without more context and maybe access to your environment. `Magick.formats` comes from ImageMagick, so I would expect to see the same thing when...

Hmm, yeah, I don't see anything suspicious there. Another thing that I'm wondering about is the `policy.xml` file. Is your passenger setup doing anything to edit the ImageMagick policy? I...

@robertleelittleiii I'm sorry, I don't know how much more we can help you with this. It doesn't strike me as an issue with RMagick. My best guess is there's some...

@robertleelittleiii one other thing to check is whether you're overriding `MAGICK_CONFIGURE_PATH` in one environment and not another. It allows you to specify where `policy.xml` is stored, so maybe it's falling...

@robertleelittleiii did you manage to resolve your issue?

I can confirm that this is still an issue on RMagick 3.1. Slight difference, though, in that `LABColorspace` has been renamed to `LabColorspace`: ```irb image = Magick::Image.new(100,100){ self.colorspace = Magick::LabColorspace...

@dlemstra thanks for looking into this! You logic seems sound, but I'm not familiar enough with the C side of things to say for sure. Maybe @Watson1978 will have a...