Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Folder Action Dispatcher

Folder Actions Dispatcher sits in memory, and grows and grows until it consumes over 2 GB. It will typically ask for as much as 50% of the CPU as well. Then it usually crashes, but not before consuming the RAM that should be available for other applications.


I did some sleuthing, and found a com.apple.FolderActions.folders.plist file in the ~Library/Launch Agents folder. Something is changing it very frequently.

Inside, the file contains the following script:


<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Label</key>

<string>com.apple.FolderActions.folders</string>

<key>Program</key>

<string>/usr/bin/osascript</string>

<key>ProgramArguments</key>

<array>

<string>osascript</string>

<string>-e</string>

<string>tell application "Folder Actions Dispatcher" to tick</string>

</array>

<key>WatchPaths</key>

<array>

<string>/Applications</string>

</array>

</dict>

</plist>


I conclude that some application somewhere is causing AppleScript to watch /Applications for changes, for some reason. I don't knowwhy this would cause Folder Actions Dispatcher to grow and grow as it does.


Questions:

  • is there a way to find the "author" or "owner" (a program) of the script and stop it?
  • I cannot delete the file -- are there innocuous changes to it that might cause it to stop behaving this way?

thank you

Mac Pro

Posted on Jul 26, 2014 9:00 AM

Reply
52 replies

Oct 22, 2014 5:39 AM in response to odontojeter2

I had the same problem, with the same solution. That is, I had several locations of .../LaunchAgents and .../LaunchDaemons in my folder actions list. After letting the system sit for about 6 hours (doing absolutely nothing), the memory usage of Folder Actions Dispatcher grew to 20 GB (yes, GB). This rendered the system pretty much unusable.


After deleting the folder actions and turning off folder actions, everything seems fine.


I've posted a bug with Apple...

Oct 25, 2014 12:18 PM in response to DragonDave

I had the same problem. After some experimenting, I discovered that Folder Actions Dispatcher started spinning when I included a "new item alert" for ~/Library/LaunchAgents. If I remove this folder from the list of Folders with Actions, then Folder Actions Dispatcher behaves itself. Currently I have actions set up for LaunchAgents and LaunchDaemons in /System/Library and /Library and for /bin. I have no idea why the one particular folder/dir causes the problem behavior. There are only five plist files in there, and none have changed since I upgraded to Yosemite.


Apple needs to fix this. Folder Actions Dispatcher is a useful security watchdog.

Oct 27, 2014 5:19 AM in response to Nidan.2006

After posting a bug with Apple, they asked me to gather some diagnostic information. This allowed me to research it a little further.


It looks like the Folder Actions Dispatcher creates its own set of files in ~/Library/LaunchAgents. One of them - com.apple.FolderActions.folders.plist - seems to constantly get updated (touched) when that folder is in the folders list. This seems to cause a bit of a feedback loop, which causes Folder Actions Dispatcher to chew up virtual RAM in a serious way.

Nov 2, 2014 5:47 AM in response to Rjkjr

Same goes for me. Every day since I upgraded from Mavericks to Yosemite, I was wondering why my iMac w/16 GB RAM would steadily swap. Activity Monitor showed that 'Folder Action Dispatcher' was occupying an obscene 13.5 GB of RAM - and growing.

To make a long story short, under Mavericks, I had written a small script as a folder action that was watching all LaunchAgent folders, in order to save them from manipulation. This was working without a hitch in Mavericks, but not so any more in Yosemite.

After disabling all folder actions, the system was healthy again.

Guess it's a bug, not a feature.

Folder Action Dispatcher

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.