Since upgrading to High Sierra (now at 10.13.6) on my Mac Pro 2012, I experience regular episodes where the process chmod eats up ~100% on all 12 cores. It happens about 15 seconds after logging in and lasts for about a minute. It then happens again later while I'm working. Of course, the computer is quite unresponsive while it lasts. In Activity Monitor I can see 12 instances of chmod using up each core.

I haven't been able to find anything with Google regarding this issue.

Can anyone help - any ideas?

System: Mac Pro 5,1 48 GB RAM 2 x 3,06 GHz 6-core Intel Xeon MacOS 10.13.6

EDIT: Having repeated boot/login while looking in Activity Monitor each time the number of chmod processes vary from 6 to 12, and other processes are (of course) also using CPU. I may have overestimated chmod usage by about 30%, the rest of CPU resources being used by the remaining processes - sorry about that. The problem remains, though.

EDIT: This is the list of entries from launchctl list that do not begin with

620 0   com.adobe.PDApp.AAMUpdatesNotifier.5964.3198F160-6F8E-4D56-84B0-E905086713D0  
628 0  
-   0   com.rogueamoeba.loopbackd  
593 0   de.rme-audio.RMEfirefaceUSBAgent  
616 0   com.leapmotion.Leap-Motion.5968  
-   0  
668 0   com.avid.ApplicationManagerHelper.5960  
603 0   com.acapelagroup.InfovoxiVoxUpdater  
604 0   com.avid.applicationmanager  
-   0   com.openssh.ssh-agent  
-   0  
622 0   com.rogueamoeba.ScheduleHelper.9032  
-   78  com.paragon-software.ExtFS.fsnotifyagent  
595 0   de.rme-audio.firefaceAgent  
598 0   com.code42.menubar  
623 0   com.native-instruments.NIHostIntegrationAgent.5976  
629 0   com.abyssoft.teleport.5972  
-   0   com.adobe.AAM.Scheduler-1.0  
-   0  
-   0   com.iconfactory.iPulse.5996  
-   0   com.paragon.updater  
601 0   com.spotify.webhelper  
615 0   jp.plentycom.boa.SteerMouse.9028  
583 0   com.prosofteng.DGMonitor  
-   0   com.Arturia.ArturiaSoftwareCenterAgent  
-   0  
-   0   com.leapmotion.Leap-Motion  
  • chmod ? and nothing else showing. – Buscar웃 Oct 10 at 20:34
  • 1
    Can you post a screen shot of activity monitor? – Allan Oct 10 at 20:41
  • chmod Change access permissions, change mode – Buscar웃 Oct 10 at 20:53
  • it should do it only once, not repeatedly, unless you or some app changes the permissions all the time – Buscar웃 Oct 10 at 20:58
  • 1
    @Buscar웃: The problem is solved. Your idea to check what was starting 'chmod' let me to use 'lsof' to investigate. 'chmod' was working on an Avid cache in 'Library/Caches'. I deleted this cache and since then, chmod hasn't been running. So thanks for your input. – CMunk Oct 12 at 9:55

I found the solution: Using lsof in Terminal located in the utility folder, I could see that chmod was accessing an Avid cache in ~/Library/Caches which I simply deleted. Now chmod doesn't run anymore.

  • 1
    you are welcome and well done. Maybe you can elaborate how did you find it, so others can profit form it. – Buscar웃 Oct 12 at 15:16
  • @Buscar웃: Do you think it needs more elaboration? I'm not sure what more to add. – CMunk Oct 13 at 19:56
  • We usually like bit more explanation for those who do not know how to do what you did. Maybe the list of your lsof ! and Library/Caches is not correct path. – Buscar웃 Oct 13 at 20:08
  • 1
    I understand. Thanks for correcting the path. Unfortunately, the output of lsof no longer exists, so I can't add it now. But I'll remember to do so in the future. – CMunk Oct 16 at 9:57

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.