Go to content

Yesterday evening I was switching this site from manual deploys to Git-based deploys, but the Gatsby build always failed because of a segmentation fault:

11:19:12 PM: (sharp:1509): GLib-GObject-WARNING **: 21:19:12.143: gtype.c:4265: type id '0' is invalid
11:19:12 PM: (sharp:1509): GLib-GObject-WARNING **: 21:19:12.143: can't peek value table for type '<invalid>' which is not currently referenced
11:19:12 PM: (sharp:1509): GLib-GObject-WARNING **: 21:19:12.143: gvalue.c:188: cannot initialize GValue with type '(null)', this type has no GTypeValueTable implementation
11:19:18 PM: /usr/local/bin/build: line 34:  1509 Segmentation fault      (core dumped) gatsby build

In the log from Netlify we can see that segmentation fault happens in sharp, a library to process images. I never had problems with sharp in the past, but after some searching I found a Github issue and sharp crashes sometimes when processing large amounts of images.

In a comment in the aforementioned issue I also found the solution for my problem. Add the following to your gatsby-node.js:

const sharp = require('sharp');


The two lines disable caching and SIMD instructions, the later provides performance benefits, but sometimes causes sharp to segfault.

If you are reading this, the build now works correctly.