POTENTIALLY DANGEROUS, but easy.Įdit these files as root: /usr/share/sandbox/mdworker.sb However, fixing the policy file is relatively easy. So maybe the policy file is wrong, or maybe mdworker shouldn't be making that call. The Sandbox policy doesn't allow that, so the worker is killed. I don't know what's really going on other than to say that mdworker (which scans and indexes files for Spotlight) calls LSCopyLibraryItemURLs() which eventually sends a message to lsboxd. Something Appple did with this latest release (also affects Mountain Lion 10.8.2). If you're seeing that, it is probably the source of the problem. Some steps may be useless, but I took all what I learn by reading different topic about slow TM and Spotlight.Ĭheck your console log file and look for lines like this (the real log lines will have process IDs and dates): sandboxd: mdworker deny mach-lookup .boxd
I opened a bugreport to Apple with the title: "TimeMachine hangs when Spotlight is in use under Mac OS X 10.7" praying that many other people will do the same to make this bug a priority. I launched a new backup using TimeMachine I waited until Spotlight finished indexing process I rebooted and then I restarted Spotlight: sudo launchctl load -w /System/Library/LaunchDaemons/.plist It may be necessary to reformat your backup drive instead of only deleting. inProgress files from my Backups.backupdb subfolders (put to trash then empty the trash is the only way to do this).
I deleted /var/folders content (see this topic to know why): sudo rm -rf /var/folders/* ( rm -rf /.Spotlight-V100/* did not work for me.) (This can also be done by excluding the whole drive using privacy setting of Spotlight and then reincluding it.) Sudo rm -rf /TimeMachineDrive/.Spotlight-V100/Store-V1 /TimeMachineDrive/.Spotlight-V100/Store-V2 /TimeMachineDrive/.Spotlight-V100/ist I deleted Spotlight index in all my drives (including the backup drives): sudo rm -rf /.Spotlight-V100/Store-V1 /.Spotlight-V100/Store-V2 /.Spotlight-V100/ist I disabled Spotlight indexing: sudo launchctl unload -w /System/Library/LaunchDaemons/.plist
Here it is (it is not a solution, only a temporary workaround to let my backup and Spotlight work until a fix is released). But apps like Safari and Google Chrome will but up there in the memory list and these will have lots of associated tasks running, each consuming a little bit of RAM.I posted this workaround in that topic. LR will always consume the largest block of memory. You may also see apps that are running that should not be (like iPhoto, iTunes etc.) You can stop these from automatically running at login. If you run that when things are slow, you can see which apps are taking up your CPU cycles. In your Applications Utility folder is an app called Activity Monitor. Many of these may be unnecessary or even unwanted. The other thing to check when LR is running slowly is to look at the other tasks that your computer has active.
One thing that could perhaps help is to upgrade to OSX10.9.2 (Mavericks) It is a free upgrade and Apple has certainly tuned the OS to run faster since 10.7. If you have lots of memory already taken up by background tasks, LR is going to slow down because it must take its turn with all of the other apps and processes running at the same time. The OS may even limit the amount of memory that can be allocated to a program. When a program asks the OS for more RAM than the computer has available, the OS will start moving some idle processes out of RAM into a swapfile (located in the 140GB free space). Sure Adobe says that 4GB is the minimum run, but they do not suggest that it will run fast with only 4GB. More importantly, I do not believe that 4GB RAM is sufficient to meet the performance needs of LR5. LR works better with more cores four would be better the the dual cores that you and I have. My MBP is the 2.9GHz i7 (a little faster) but I have the max for my MBP of 8GB RAM. I think all of the above might be a contributor.