In any case, I'm not sure if they're symptomatic, or just a red-herring. "StandardErrorPath" = "/var/log/watchdogd/log" "StandardOutPath" = "/var/log/watchdogd/log" Interestingly the -43 code on Watchdogd doesn't match the output of launchctl list: sudo launchctl list launchctl list | grep -v "\t0\t"Ģ8122 -15 sudo launchctl list | grep -v "\t0\t" I did a quick check through all the launchd daemons to find any error codes.
_DirtyJetsamMemoryLimit key is not available on this platform. This helps to avoid host process crash in event of a COM object crash. The legitimate version is developed by Microsoft and its purpose is to run COM objects aside from original processes that request them.
Nothing significant in the logs that I can see: the most frequent message:ġ1/6/14 10:06:38.748 PM : COM SURROGATE (dllhost.exe) is generally recognized as a legitimate Windows process, although it can also be a malware in disguise. It has the highest cpu time on the box, 3 times that of kernel task, and vastly higher than Plex which is genuinely CPU heavy - video transcoding, and it supports a lot of clients in the house running frequently. This issue is basically caused, when the skype is running in the background or one of the reason might also be that you are using windows skype app. Since the Yosemite upgrade I can't change the log level with 'sudo launchctl log level debug'Ĭhecking top or Activity Monitor I can see that launchd itself is using the CPU heavily, not a process which it's spawning off.
0 kommentar(er)
