I often have trouble with my Macbook Air not staying asleep…decided to check the Console and found something I hadn’t seen before: KM was “caught causing excessive wakeups.” The below are from a search for Keyboard in the log file:
5/26/15 7:00:47.000 PM kernel[0] Apple Internal Keyboard / Trackpad::start Start Succeeded
5/26/15 7:01:09.947 PM Keyboard Maestro Engine[336] Keyboard Maestro Engine: Daemon launched by login window. Initiating login actions.
5/26/15 7:01:19.027 PM Keyboard Maestro Engine[336] Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"
5/26/15 7:01:19.285 PM Keyboard Maestro Engine[336] Bartender: Loaded BartenderHelperNinety
5/27/15 2:13:07.000 AM kernel[0] process Keyboard Maestro[336] caught causing excessive wakeups. Observed wakeups rate (per sec): 208; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 101928
5/27/15 9:11:47.629 AM Keyboard Maestro[1636] Keyboard Maestro: Engine is already running
5/27/15 9:11:48.512 AM Keyboard Maestro[1636] Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: "/Library/ScriptingAdditions/SIMBL.osax"
5/27/15 9:11:48.000 AM kernel[0] Keyboard Maestro (map: 0xffffff8033c76960) triggered DYLD shared region unnest for map: 0xffffff8033c76960, region 0x7fff94200000->0x7fff94400000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
Thoughts?
Thanks,
A