Large (>1MB) colour profiles can crash with segmentation fault

Hi,

We are experiencing node/express server crash when using sharp with specific images (4): segmentation fault

I’ve tried to go from using Buffer to Stream without any change. I’ve tried to isolate the problem without doing anything on the image like this:

const sharp = require('sharp');

sharp('./images/bug.jpg')
  .toFile('./images/out.jpg', (err, info) => {
    console.log({ err, info });
  });

here is one of the images: https://framapic.org/pRRvN4QD9sK4/akysnsC4rj15.jpg

Working locally with OSX Sierra, node 6.11.1, & same problem remotely with google gcp instances.

Thanks for helping

[lovell]

Brilliant, thank you, it looks like you’ve run into https://github.com/jcupitt/libvips/commit/7b64246af2cdf9c7b9fae0f29e5483bb6a7376d2 which was fixed in libvips 8.5.6.

This explains why the pre-compiled libvips binaries (8.5.5) fail and brew-installed libvips (8.5.9) works.

[lovell]

An OS-level backtrace is required here rather than a JS stacktrace.

As I mentioned above, gdb is probably the best tool for this.

You use it by running gdb --args /usr/bin/node your-app.js, enter run at the prompt, wait for the crash then enter bt at the prompt for the backtrace.