Altă chestie în Mavericks.
Vorbeam de com.apple.iconService. Halește juma’ de giga de memorie, da’ nu face numai asta: mai scrie și un giga jumate de cache. Asta-i bună! Nici eu, dacă programam, nu făceam un lucru mai prost, mai lent și mai lacom!

Dupa 2-3 zile ajunge la vreo 50 mega; la cache nu m-am uitat pana acum.

la mine are 10mb de memorie ocupata.
ce este si ce face?

Ia vedeti ce spun astia pe aici: https://discussions.apple.com/thread/5472367?start=45&tstart=0

Problema mea nu e la procesor, ci la memorie.

Eu nu am avut inca problema, nu o pot reproduce. Speram ca solutiile lor sa fie folositoare. Oricum, concluzia generala este ca IconService Agent scrie in /var/folders/xx unde “xx” este un nume care difera la fiecare user si la fiecare instanta de pornire a sistemului. Acel folder cu nume variabil poate sa-si piarda sau corupa permisiile. De acolo “incapatanarea” lui IconService Agent sa scrie ceva unde nu i se mai permite. Comanda “mkdir ${TMPDIR}/com.apple.IconServices” in terminal va transforma com.apple.IconServices in fisier temporar, care va fi sters la urmatorul restart de sistem.

Cum golesc cache-ul? In afara sa pornesc maintenance la săptămana?

Mergi in /Users/Tu/Library/Caches selectezi tot si arunci la cos, apoi restart si golit cosul. Dureza ceva. Pentru sistem, la fel, doar ca mergi in /Library/Caches, iar acolo va trebui sa dai acces prin parola.
Programe ca iCare (gratuit in MacAppStore) sau MacBooster (pe bani, dar merita) marcheaza toate fisierele din cache ca temporare, sistemul va scrie un cache nou, dupa restart (sau shutdown, atunci cand vrei tu) la turn on fisierele cache temporare sunt sterse. Deci nu esti obligat sa restartezi sistemul, daca asta este frustrarea ta.

@Iaru:
Ia vezi cum merge daca faci ce zice aici:

Some of these steps may not be necessary, but here are all of the steps I took that inadvertently put IconServicesAgent back in its place. Note: all commands are a single-line, if they appear to be multiple that’s just the forum formatting.
  1.  Check for any QuickLooks related .plist files. In a terminal: mdfind com.apple.quicklook. -name .plist
  2.  I only had files at the system level (specifically within /System/Library/LaunchAgents/). If you have others, modify the directions below to take that into account (re-introducing plist files from the system level back up to the user).
  3.  Make some temporary directories to store these plist files, just in case: mkdir ~/tmp-quicklook
  4.  Kill the IconServicesAgent: killall -KILL com.apple.IconServicesAgent
  5.  Move the plist files to temporary directories: sudo mv /System/Library/LaunchAgents/com.apple.quicklook.* ~/tmp-quicklook/
  6.  Reset QuickLook generators and disk cache: qlmanage -r && qlmanage -r cache
  7.  Reboot
  8.  Move plist files back: sudo mv ~/tmp-quicklook/com.apple.quicklook.* /System/Library/LaunchAgents
  9.  Reboot
From this point on you shouldn’t see IconServiceAgent ever go above 30MB on the memory tab; Twitter is actually consuming more memory than IconServiceAgent is right now! You will continue to see entries in your logs but they should only occur once per file type, roughly. I found just scrolling through “All My Files” in Finder really quick took care of most everything and after another reboot and repeating this process - I saw very few, if any, new entries.