Apple Intelligence now features Image Playground, Genmoji, Writing Tools enhancements, seamless support for ChatGPT, and visual intelligence.
Apple Intelligence has also begun language expansion with localized English support for Australia, Canada, Ireland, New Zealand, South Africa, and the U.K. Learn more >
Apple Intelligence has also begun language expansion with localized English support for Australia, Canada, Ireland, New Zealand, South Africa, and the U.K. Learn more >
You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
I am recently having problems with getting out of free memory. I inspected processes in Activity Monitor and found that a tccd process is using over 1Gb (once almost 1.5Gb) RAM.
MacBook Pro (13-inch, Mid 2012), OS X Mountain Lion (10.8.2), 4Gb RAM
When you googled 'tccd process Mac' what did you get?
https://www.google.com/search?q=tccd+process+mac&ie=UTF-8&oe=UTF-8&hl=en&client= safari
Well, nothing useful.
Back up all data.
Triple-click the line below to select it:
~/Library/Application Support/com.apple.TCC/TCC.db
Right-click or control-click the highlighted line and select
Services ▹ Reveal
from the contextual menu. A Finder window should open with a file selected. Move the selected file to the Desktop, leaving the window open. Log out, log back in, and test. If there's no change, put the file you moved back where it was, overwriting the one that may have been created in its place. Then log out again. Otherwise, delete the file you moved.
I had a similar problem in which tccd was consuming a lot of CPU and memory. The underlying problem turned out to be related to broken rules in Hazel. I documented it here:
I had the same problem. The tccd process took more and more of the memory.
The culprit however was a launchagent I had created. This launchagent watched a folder and was always kept alive.
The launchagents task was to run a shell script and was being called all the time.
I have no more tccd problem since I have changed this launchagent.
So if you have this problem, I advise to have a critical look at the launchagents or launchdaemons (~/Library/LaunchAgents/, /Library/LaunchAgents/ or /Library/LaunchDaemons/).
tccd process using over 1Gb RAM
