KM Editor and Engine Sluggish Response and Show Very High CPU

Continuing the discussion from FaceTime Audio Caller with Pop Up Contact List (KM 8.2.3):

@peternlewis:

Running Keyboard Maestro 8.2.3 on macOS 10.12.6

Although the above macro may have nothing to do with this issue, I started experiencing no response from KM Engine, and very sluggish response from KM Editor after I tested the macro that uses FaceTime. Here's a screenshot of Activity Monitor:

image

The KM Engine actually was as high as 98%+.

I tried restart of KM Engine and App, but ended up having to restart my Mac. Here's the KM Engine log (last 400 entries) during this time period:

KM Log High CPU No Response 2018-08-05 JMichaelTX.txt.zip (3.2 KB)

I did notice quite a few entries like this:

2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0
2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0
2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0
2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0
2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0
2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0
2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0
2018-08-05 18:40:57 Assertion Failed: r,  file: /Users/peter/Keyboard Maestro/Project/Source/XCAF/XRunningApplicationsList.mm:148, value: 0

There may be other, but that was the only suspicious entries I noticed.

Here's another possibility related report:

Get a sample with Activity Monitor to see where it is spending its time.

That assertion seems to indicate that Keyboard Maestro cannot find the front application’s path. At least that looks like the most likely case where that assertion fires without any other assertion firing.

KM seems fine now. That event was the only time I can remember KM ever being sluggish. If it happens again, I'll try to get a sample for you.