gatsby: GLib-GObject-CRITICAL error with last gatsby-transformer-sharp

I dig a bit more and it looks to start crashing starting from gatsby-plugin-sharp@2.2.15 so temporary downgrading to gatsby-plugin-sharp@2.2.14 will do a trick.

It looks to be caused by upgrading sharp from ^0.22.1 to ^0.23.0

I event don’t know who to @ mention here as this PR was created by @renovate-bot and merged by @gatsbybot 😄

Try adding these at the top of your gatsby-nodes.js:

const sharp = require('sharp')
sharp.simd(false)
sharp.cache(false)

See #6291 (comment)

I just tried this and am still having the same error:

(sharp:44423): GLib-GObject-WARNING **: 11:24:41.418: cannot register existing type 'VipsObject'

(sharp:44423): GLib-CRITICAL **: 11:24:41.418: g_once_init_leave: assertion 'result != 0' failed

(sharp:44423): GLib-GObject-CRITICAL **: 11:24:41.418: g_type_register_static: assertion 'parent_type > 0' failed

(sharp:44423): GLib-CRITICAL **: 11:24:41.418: g_once_init_leave: assertion 'result != 0' failed

@hhimanshu @klgh

You both look to not downgrade actually, the version range you specify "gatsby-plugin-sharp": "^2.2.12" includes 2.2.16. You can even see that in npmPackages output:

gatsby-plugin-sharp: ^2.2.12 => 2.2.16 - notice, that 2.2.16 is actually used.

Try pinpointing it directly to "2.2.12".

Also, you may try removing yarn.lock or npm-lock.json and node_modules and install deps again.

Downgrading to gatsby-plugin-sharp@2.2.14 fixes the issue.

I just had this problem after upgrading an old project (a few months old). What seems to have worked around it for me was switching to Yarn, with the resolutions config above (https://github.com/gatsbyjs/gatsby/issues/16957#issuecomment-526824124) and then:

rm -rf node_modules/sharp/vendor
yarn install
yarn upgrade
yarn start

For me the issue was gatsby-plugin-favicon depending on a different version of sharp:

├─┬ gatsby-plugin-favicon@3.1.6
│ └─┬ favicons-webpack-plugin@0.0.9 (git+https://github.com/Creatiwity/favicons-webpack-plugin.git#0872de414061baaad0a2853c77ae75bc38b8bbbf)
│   └─┬ favicons@5.4.1
│     └── sharp@0.22.1
├─┬ gatsby-plugin-manifest@2.2.29
│ └── sharp@0.23.3 
├─┬ gatsby-plugin-sharp@2.3.3
│ └── sharp@0.23.3 
└── sharp@0.23.3 

Removing that plugin solved my issue with this…

@LekoArts Should this really be closed? Seems like this is an ongoing issue.

Thanks @sidharthachatterjee! Appending

"resolutions": {
  "sharp": "0.22.1"
}

to package.json and reinstalling node_modules worked as a temporary fix.

May I suggest that this issue be reopened as long as people are still running into it?

@RomanHotsiy Thanks for investigating! Let’s wait on @lovell (Sharp maintainer) to see if this is a known issue before we merge in https://github.com/gatsbyjs/gatsby/pull/16971

In the mean time, sorry for the trouble, folks! Please use gatsby-plugin-sharp@2.2.14 or set the following in your package.json (when using yarn)

  "resolutions": {
    "sharp": "0.22.1"
  }

I spent 2 days on this issue and here’s how I finally found salvation

• I switched to yarn - did nothing
• I cleared node_modules rand gatsby clean did nothing
• I was having issues with node so I reverted from node 12 to node 10 (that fixed another issue I was having)

$ npm i node@10.15.3 -g

• I did $ npm rebuild (did nothing)
• I was desperate and tried audit fix (did nothing)
• I uninstalled gatsby-plugin-favicon (did nothing - so reinstalled it)

Then I had GLib GObject-CRITICAL errors and I checked for different versions of sharp using

$ npm up

and

$ npm ls sharp

• I downgraded gatsby-plugin-sharp (did nothing)

In the end I believe from my google searching that the issue resides with different versions of sharp

• And that will show that sharp versions are off

I looked at the gatsby-transformer-sharp and it’s version was off so I saw in the repo that it has the correct version of sharp but my gatsby-transformer-sharp was an older version. I upgraded to

$ npm i gatsby-transformer-sharp@2.3.2

• ANd now I get

• Now I ran $ gatsby develop and life was great again. Hope this helps other Gatsby JS shipmates to avoid code sea sickness. Ahoy!

I’m not really sure we’ve found the real cause of this issue, https://github.com/gatsbyjs/gatsby/issues/16957#issuecomment-526824124 worked for us but we’re now stuck with sharp 0.22.1 (and warnings).

None of the above suggestions (npm rebuild mainly) worked on our end.

Hi guys,

I’m afraid that I’m still experiencing this issue.

I’ve tried the latest version of the libraries in question, as well as a number of permutations in between. I’ve also tried clearing node_modules and npm rebuild, but still can’t get past this one.

gatsby info

System:
    OS: macOS 10.14.5
    CPU: (8) x64 Intel(R) Core(TM) i7-4980HQ CPU @ 2.80GHz
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.16.0 - ~/.nvm/versions/node/v10.16.0/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.16.0/bin/npm
  Languages:
    Python: 3.7.0 - /usr/local/bin/python
  Browsers:
    Chrome: 76.0.3809.100
    Firefox: 68.0.1
    Safari: 12.1.1
  npmPackages:
    gatsby: ^2.9.0 => 2.13.82
    gatsby-image: ^2.1.3 => 2.2.14
    gatsby-link: ^2.1.1 => 2.2.9
    gatsby-plugin-catch-links: ^2.0.15 => 2.1.5
    gatsby-plugin-facebook-pixel: ^1.0.3 => 1.0.3
    gatsby-plugin-feed: ^2.2.3 => 2.3.9
    gatsby-plugin-google-analytics: ^2.0.21 => 2.1.11
    gatsby-plugin-google-tagmanager: ^2.0.15 => 2.1.7
    gatsby-plugin-manifest: ^2.1.1 => 2.2.9
    gatsby-plugin-nprogress: ^2.0.10 => 2.1.4
    gatsby-plugin-offline: ^2.1.1 => 2.2.10
    gatsby-plugin-preact: ^3.0.0 => 3.1.6
    gatsby-plugin-react-helmet: ^3.0.12 => 3.1.5
    gatsby-plugin-s3: ^0.3.2 => 0.3.2
    gatsby-plugin-sass: ^2.0.11 => 2.1.12
    gatsby-plugin-sharp: 2.2.16 => 2.2.16
    gatsby-plugin-sitemap: ^2.1.0 => 2.2.9
    gatsby-plugin-twitter: ^2.0.13 => 2.1.4
    gatsby-plugin-web-font-loader: ^1.0.4 => 1.0.4
    gatsby-remark-autolink-headers: ^2.0.16 => 2.1.7
    gatsby-remark-component: ^1.1.3 => 1.1.3
    gatsby-remark-copy-linked-files: ^2.0.13 => 2.1.11
    gatsby-remark-external-links: ^0.0.4 => 0.0.4
    gatsby-remark-images: ^3.0.14 => 3.1.18
    gatsby-remark-images-contentful: ^2.0.12 => 2.1.10
    gatsby-remark-lazy-load: ^1.0.1 => 1.0.1
    gatsby-remark-responsive-iframe: ^2.1.1 => 2.2.8
    gatsby-remark-smartypants: ^2.0.9 => 2.1.5
    gatsby-source-contentful: ^2.0.67 => 2.1.28
    gatsby-source-filesystem: ^2.0.39 => 2.1.17
    gatsby-source-wordpress: ^3.0.65 => 3.1.24
    gatsby-transformer-json: ^2.1.11 => 2.2.5
    gatsby-transformer-remark: ^2.3.12 => 2.6.19
    gatsby-transformer-sharp: 2.2.12 => 2.2.12

It doesn’t look like there are any conflicting versions of sharp in the tree, see below.

npm list sharp

├─┬ gatsby-plugin-manifest@2.2.9
│ └── sharp@0.23.0
├─┬ gatsby-plugin-sharp@2.2.16
│ └── sharp@0.23.0  deduped
├─┬ gatsby-remark-images-contentful@2.1.10
│ └── sharp@0.23.0  deduped
├─┬ gatsby-source-contentful@2.1.28
│ └─┬ gatsby-plugin-sharp@2.2.18
│   └── sharp@0.23.0  deduped
└─┬ gatsby-transformer-sharp@2.2.12
  └── sharp@0.23.0  deduped

Any ideas on where to go next?

Could people try running npm rebuild?

@dcsan I would call that a workaround rather than a solution since people will keep running into this problem if it requires manual work to avoid. Also, what would be the yarn equivalent to this? I tried yarn upgrade but that didn’t work for me, resulting in continued version mismatch:

➜  yarn list --pattern sharp
yarn list v1.17.3
├─ favicons@5.4.1
│  └─ sharp@0.22.1
├─ gatsby-plugin-sharp@2.2.27
├─ gatsby-transformer-sharp@2.2.19
└─ sharp@0.23.1

I documented a fix for this on some other ticket. basically it’s caused by two mismatching versions of ‘sharp’ which are deps of other packages.

npm up
npm ls sharp

fixed it for me at least

I had the same issue on Netlify but got it working by:

1. downgrade gatsby-plugin-sharp to 2.2.14 (gatsby-plugin-sharp@2.2.14)
2. rm package-lock.json
3. rm yarn.lock

then push your changes. if the build fails again then in netlify you will have to click on the failed build click on retry deploy then Clear cache and deploy site

I can confirm that rolling all dependencies that make sure of Sharp to ones that use 0.21.1 avoids the issue, but clearly, this is not a long term solution.

npm list sharp 

├─┬ gatsby-plugin-manifest@2.2.6
│ └── sharp@0.22.1
├─┬ gatsby-plugin-sharp@2.2.13
│ └── sharp@0.22.1
├─┬ gatsby-remark-images-contentful@2.1.5
│ └── sharp@0.22.1  deduped
└─┬ gatsby-transformer-sharp@2.2.7
  └── sharp@0.22.1  deduped

well that’s unfortunate that favicons still seems stuck on an old sharp. perhaps it’s down to the semver upgrade funnily enough I have favicons working in my project, but without that dependency.

As far as I can tell it’s a very deep problem to have two versions of sharp co-existing. We’re dependent on the packages updating to use the same sub-deps of sharp.

also FWIW I stopped using yarn because of various problems with C extensions and native compiling. npm also has a cache now so i think the speed difference isn’t so noticeable.

I just installed latest favicons and indeed get that same problem.

➜  dc.rik.ai git:(master) ✗ yarn list --pattern sharp
yarn list v1.17.3
├─ favicons@5.4.1
│  └─ sharp@0.22.1
├─ gatsby-plugin-sharp@2.2.27
├─ gatsby-transformer-sharp@2.2.19
└─ sharp@0.23.1
✨  Done in 8.55s.

my app will still start but I guess it’s because of the image cache or sharp not getting triggered.

➜  dc.rik.ai git:(master) ✗ rm -rf .cache
➜  dc.rik.ai git:(master) ✗ npm start

however still starts… so it’s hard to even know how to trigger this nasty problem. probably running the whole install process again.

from my side I just removed the favicons package for now, as I seem to have favicons anyway.

solution here: https://github.com/gatsbyjs/gatsby/issues/9751#issuecomment-533702498

npm up
npm ls sharp

check you don’t have any version mismatches with sharp.

I’m getting identical problems here with latest versions of related plugins

    "gatsby-plugin-sharp": "^2.2.24",

Whats your installed libvips version? And please try running npm rebuild, your issues occur most likely due to the fact that your newly installed binary doesn’t work with the installed libvips version on your machine. There should be no need to downgrade the version of gatsby plugins 😃

I have this same issue and none of these suggestions has worked for me…I see reference to gatsby-plugin-sharp but we are not using this plugin anywhere. however I have added this and still yet not working… Could someone please help:

success run static queries - 0.098 s — 6/6 84.00 queries/second success run page queries - 1.525 s — 70/70 46.86 queries/second ⠙ start webpack server

(sharp:19129): GLib-GObject-WARNING **: 13:45:01.948: cannot register existing type ‘VipsObject’

(sharp:19129): GLib-CRITICAL **: 13:45:01.948: g_once_init_leave: assertion ‘result != 0’ failed

(sharp:19129): GLib-GObject-CRITICAL **: 13:45:01.948: g_type_register_static: assertion ‘parent_type > 0’ failed

(sharp:19129): GLib-CRITICAL **: 13:45:01.948: g_once_init_leave: assertion ‘result != 0’ failed

This is looking resolved with the latest release for gatsby and version 2.2.16. Thanks all, and happy to close this 😃

@sidharthachatterjee I think the problem is that sharp was cached and when using npm install it internally uses npm build and the postinstall scripts will use the npm cached values,npm rebuild will not use the cached values

You’re right though about CircleCI, I’m not sure why I had problems there

Try adding these at the top of your gatsby-nodes.js:

const sharp = require('sharp')
sharp.simd(false)
sharp.cache(false)

See https://github.com/gatsbyjs/gatsby/issues/6291#issuecomment-509783902