2
2
I've noticed my system.log is getting flooded with messages like this:
May 5 12:56:08 macpro com.apple.launchd[1] (com.apple.qtkittrustedmoviesservice[8568]): Exited: Killed: 9
May 5 12:56:08 macpro kernel[0]: memorystatus_thread: idle exiting pid 8568 [qtkittrustedmovi]
May 5 12:56:11 macpro com.apple.launchd[1] (com.apple.audio.ComponentHelper[8564]): Exited: Killed: 9
May 5 12:56:11 macpro kernel[0]: memorystatus_thread: idle exiting pid 8564 [com.apple.audio.]
May 5 12:56:12 macpro com.apple.launchd[1] (com.apple.sleepservicesd[8572]): Exited: Killed: 9
May 5 12:56:12 macpro kernel[0]: memorystatus_thread: idle exiting pid 8572 [SleepServicesD]
May 5 12:56:12 macpro com.apple.launchd[1] (com.apple.audio.SandboxHelper[8563]): Exited: Killed: 9
May 5 12:56:12 macpro kernel[0]: memorystatus_thread: idle exiting pid 8563 [com.apple.audio.]
I understand launchd might kill processes when RAM is full, but I think I have plenty of RAM (32GB). I'll usually have a very small amount of free memory, but there is always over 15GB "inactive" memory when I check Activity Monitor. This isn't really causing any problem, but I'd like to declutter my log file so I can see real problems more easily.
That looks like a report of exit status (that the process was killed), not necessarily that launchd itself killed it. – Kevin Reid – 2013-05-06T02:08:15.580
Not sure I agree... but if that's the case, do you know how to see what's killing the processes? – Elliott B – 2013-05-06T05:43:50.203