10 Replies Latest reply: Oct 27, 2015 4:52 AM by Matroskin
A Sneaky Hippo Level 1 (0 points)

After recently upgrading to Mountain Lion I now have the process named "parentalcontrolsd" running 24/7 even though I do NOT use any parental controls. Everything is turned off for every user account on this MacBookPro. I've enabled/disabled these setting and then shutdown the machine etc but all to no avail. Below is a capture from Activity Monitor:

 

58174 parentalcontrolsdroot98.7972.3 MBIntel (64 bit)138.4 MB

 

Any reason why this is happening? Was never an issue before upgrading to Mountain Lion..

 

Thanks in advance


MacBook Pro, OS X Mountain Lion (10.8.2)
  • berkant Level 1 (0 points)

    I have exactly the same problem.

     

    Some Forums recommend to disable parental controls in order to get this fixed.

     

    But this is definetly not an option for me.

    The situation is not acceptable as the battery on my mac book is draining very fast having a process taking up to 100% CPU.

     

    Would be great if someone could point out a solution.

     

    Thanks

  • berkant Level 1 (0 points)

    I think i just found a solution:

     

    1. Disable parental controls on all users.

    2. delete the folder /Library/Application Support/Apple/ParentalControls

    3. restart Mac

    4. enable parental controls again

     

    This solution works perfectly for me. The parentalcontrolsd process is not eating much CPU anymore.

     

    Hope this helps

  • Patrick Tosa Level 1 (0 points)

    Had the same problem as described above; parentalcontrolsd process took over all available CPU with no active accounts running parental controls.  Had Parental Control turned on for Guest account even though it was disabled.  Followed berkant's solution and it worked perfectly!!   Mac Mini now running at top speed.

  • Why Did I believe???? Level 1 (0 points)

    I had the same issue but found it was related to Picasa and sync of web albums.

    Killed Picasa and all was fine, restarted Picasa and back it came.

  • lisdavid89 Level 1 (10 points)

    I use to have parental controls enabled, but then I removed the accounts that I no longer needed which caused the problem of parentalcontrolsd eating 50% CPU, which usually resulted in either a login crash or several minutes to log in. Console showed parentalcontrolsd panicking since it couldn't find the old enabled settings (since they were turned off and removed). I basically have over 1500 parentalcontrolsd error messages in console. I followed berkant's solution of clearing the folder and now everything works great! No more login crashes and things run much faster! Kudos for the solution!

  • toadc Level 1 (0 points)

    thanks, Berkant.

    worked for me.

    OS X 10.8.2

  • jesup Level 1 (0 points)

    Worked for me too (10.7.5).  Amazing this sort of thing has been around for so many years (reports go back to 2008 or 2007 or earlier)

  • jackfromgreer Level 1 (0 points)

    Thanks berkant!

     

    This solved to probem as described. (This had been driving me crazy!)

  • Mojojojo_ Level 1 (0 points)

    THANK YOU Berkant!

     

    this solved my issue perfectly!

     

    if only i had checked before i spent the last two days wasting my time in and out of my local Apple store which was zero help.

     

    Does anyone know what caused this issue to begin with?

     

    My MBP never had this issue only untill a few weeks ago when every time i turned it on, few mintues later the fans kicked in and the computer over heated anough to cook eggs on it- Was very worried!

     

    So relieved. Thanks again Berkant!

  • Matroskin Level 1 (0 points)

    Berkant, thank you!

    Worked for me in El Capitan!