Google Chrome Helper 'Libnotify: registration failed with code 9 on line 2835' error troubles some macOS Big Sur users

When it comes it web browsers, Google Chrome takes the lead. Not only does it promise fast load speeds, but it also comes with support for extensions that enable surfing the web with more capabilities.

Not only it is available for Google products like Android and Chrome OS, but it also has a decent share of the market on Windows, macOS, and Linux.

A part of the Chrome browser is Google Chrome Helper. It is an interface bridge that allows external plug-ins to work on your browser.

If you’re a MAC user, then you must have seen the Chrome Helper in the Activity Monitor menu.

That being said, a bug has appeared for the Google Chrome Helper. Users are complaining about getting ‘Libnotify: registration failed with code 9 on line 2835’ error.

Apart from this error, the Chrome Helper is also the culprit behind performance degradation and high CPU load.

Multiple users have posted their concerns on Google Chrome support forum and we have captured some of them below.

I discovered my Mac does the same error. It looks like it’s occurring exactly every minute according to /var/log/system.log
Trying the workaround of disabling hardware acceleration did not work.

Line in log: “Google Chrome Helper[some#]: Libnotify: notify_register_coalesced_registration failed with code 9 on line 2835”
Source

Yes, I have the same error. I just updated to Mac OS 11 and was fixing some other software when I saw this message being spammed in the log file.

Google Chrome Helper[3783]: Libnotify: notify_register_coalesced_registration failed with code 9 on line 2835
Source

Chrome Helper ‘Libnotify: registration failed’ error was also posted on the Chromium forum. It seems like the error mostly appears for macOS Big Sur users and didn’t exist before.

AFAIK notify_register_coalesced_registration doesn’t exist pre-Big Sur and I’m not setup to dig around the dyld cache yet
Source

And apparently, it seems this has something to do with the sandbox and that there is nothing the Chrome department can do on their end. Granted, it means that Apple and macOS Big Sur are likely the culprits.

There is no workaround yet, however, we will keep you posted whenever there is an update regarding Chrome Helper ‘Libnotify: registration failed’ error.

In the meantime, you can check out our dedicated bug tracker to know more about the status of various bugs and issues that popped up after the macOS Big Sur update.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.