ReportCrash spamming "Failed to start process notifications for pid"

Hi! This is my first post, I apologize in advance for any faux pas.

Primary issue: I'm getting periodic high ReportCrash CPU usage.

I opened up Console.app and find out that ReportCrash is spamming this error message: "Failed to start process notifications for pid #" ReportCrash seems to be showing that the error is from CoreSymbolication.

The pid # in the error messages are in increasing order, and none of the pid number can actually be found in Activity Monitor CPU tab. They looks like this:

User uploaded file

The machine is an Early-2015 13-inch MacBook Pro; 3.1 GHz Intel i7; 16 GB DDR3. I'm running macOS High Sierra ver 10.13.5

I'm thinking about force-quitting coresymbolicationd, but thinking it's a private framework and probably kernel related I haven't tried that.


Anyone has any ideas?

Thanks!

MacBook Pro, macOS High Sierra (10.13.5)

Posted on Jun 25, 2018 5:38 AM

Reply

Similar questions

There are no replies.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

ReportCrash spamming "Failed to start process notifications for pid"

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.