Celapid process consuming 100% CPU

  • 1
  • Problem
  • Updated 6 years ago
  • Solved
I'm not sure what caused this, but I noticed recently that there's a process called "celapid" on my computer which is always running, can't be killed permanently, and which consumes 100% of my CPU. It's pretty annoying because I think it's killing my battery life, and I can't do anything about it.

Is this process part of the CE software?

I installed the new Mac beta about a week ago, and then noticed this and tried to revert to the last stable version, but it doesn't seem to have fixed this problem.

Any help would be greatly appreciated!
Photo of Stephen Martinis

Stephen Martinis

  • 2 Posts
  • 0 Reply Likes
  • annoyed

Posted 6 years ago

  • 1
Photo of Chad

Chad, Alum

  • 122 Posts
  • 10 Reply Likes
Hi Stephen,

Covenant Eyes does not have a process entitled celapid. I performed a google search for a process by that name and I was unable to find anything at all.

I'm sorry I haven't been much help other than to let you know Covenant Eyes isn't the culprit. If you do find out where the celapid process originated please post the information here, we love to learn knew things.

Chad
Photo of Stephen Martinis

Stephen Martinis

  • 2 Posts
  • 0 Reply Likes
Hi Chad,

Thanks for answering me!

The reason I thought it was related to covenant eyes is because the launchd entry in "/Library/LaunchDaemons/" is called com.cvnt.celapid.plist, and the Covenant eyes daemon is called com.Cvnt.daemon.plist, so I thought they might be related.

I looked at the time that my computer says the file was created, and it says on April 9th. I looked at my web browser, and I wasn't visiting a website then, so I'm confused as to how it got created.

If it's not from covenant eyes, then I'll look elsewhere to find out where it's from.

Thanks!

Stephen

Photo of jlbang

jlbang

  • 3 Posts
  • 0 Reply Likes
I also have a "celapid" process running on my Mac. It's installed at /usr/libexec/celapid. I have the same LaunchDaemon's file that Stephen had. The files at  /Library/LaunchDaemons/com.cvnt.cehostsd.plist and  /Library/LaunchDaemons/com.cvnt.celapid.plist have exactly the same modified dates on my machine, so I can't see how they wouldn't have come together. Furthermore, It's the exact date and time I upgraded to CE 2.5.1.

I used Activity Monitor to take a sample of celapid and I'm seeing calls in the processes to things like CEGenericTransportServer::acceptClient() and CEGenericTransport.
2781 boost::_bi::bind_t<void, boost::_mfi::mf0<void, ActivityLoggingHandler>, boost::_bi::list1<boost::_bi::value<ActivityLoggingHandler*> > >::operator()()  (in celapid) + 63  [0x1000f8f2f]
                  2781 void boost::_bi::list1<boost::_bi::value<ActivityLoggingHandler*> >::operator()<boost::_mfi::mf0<void, ActivityLoggingHandler>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ActivityLoggingHandler>&, boost::_bi::list0&, int)  (in celapid) + 85  [0x1000f8fb5]
                    2781 boost::_mfi::mf0<void, ActivityLoggingHandler>::operator()(ActivityLoggingHandler*) const  (in celapid) + 114  [0x1000f9052]
                      2781 ActivityLoggingHandler::acceptClients()  (in celapid) + 606  [0x1000f67de]
                        2781 CEGenericTransportServer::acceptClient(CEGenericTransport*&)  (in celapid) + 27  [0x1000b07cb]
                          2781 OS_acceptSocketConnection(int)  (in celapid) + 30  [0x1001348ee]
                            2781 __accept  (in libsystem_kernel.dylib) + 10  [0x7fff89316e02]
 
Are you sure this isn't Covenant eyes? Seems pretty open-and-shut that it is. Either that, or you guys have a virus piggy-backing on your stuff.
Photo of jlbang

jlbang

  • 3 Posts
  • 0 Reply Likes
Here's a link to the sample: http://pastebin.com/4J8urHQD
Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Official Response
Hey Jibang,

Celapid IS a Covenant Eyes process. 

A little background, when this post first came to light we had recently done some improvements on Mac which had included this process, that information however had not yet made it out of dev land and into general knowledge.

The initial problem of celapid eating up a lot of memory/processing power was quickly fixed and I thought we had come back here to update the post, which we clearly did not...  (oops)

Sorry about any confusion,
Photo of jlbang

jlbang

  • 3 Posts
  • 0 Reply Likes
OK, thank you John! It wasn't eating tons of resources, so I agree that you probably did fix that issue. I just noticed it and went "Bwah?" and of course, if it didn't belong to you, I was going to be really scared.
Photo of John

John, Official Rep

  • 439 Posts
  • 79 Reply Likes
Glad to know it was fixed, thanks for the feedback
 
To be honest i had the same reaction (bwah?) when I saw your post and realized that we had never clarified that celapid was related to us....