saor47 Posted March 14 Share Posted March 14 When I type an 'e' in the search box, it causes Alfred to freeze 1-2 seconds. After a few tests, I found out: It only occurs when the letter 'e' is typed at the very beginning of a search string, no matter if there's more text behind this 'e'. It occurs not only right after the search bar appears. After each time the lag appears, the 'e' stops causing any lagging for about half a minute, before it occurs again (feels like cache?). No error is shown in the workflow debug console. No other key stroke causes the same problem. It doesn't appear in any other app. What I've tried to rule out: Quit other apps which do keyboard mapping Disable all workflow keywords starting with an 'e' Clear application cache & rebuild macOS metadata Restart Alfred None of these worked. When searching a single 'e', all I got in results were only just applications and web searches, altogether less than 10. This is really bizarre and I have no idea... Link to comment Share on other sites More sharing options...
pixelgeek Posted March 14 Share Posted March 14 Try disabling all the workflows and see if it still does it. Link to comment Share on other sites More sharing options...
Stephen_C Posted March 14 Share Posted March 14 If the previous suggestion doesn't help try typing ?e into Alfred's search box to search Alfred's preferences and see if that provides any clue. Stephen Link to comment Share on other sites More sharing options...
Andrew Posted March 14 Share Posted March 14 @saor47 could you please send the exported output of typing ?diagnostics into Alfred to our info@ address so I can take a look? Put a link to this forum thread in the email. Thanks, Andrew Link to comment Share on other sites More sharing options...
saor47 Posted March 17 Author Share Posted March 17 @Andrew Have done that. Link to comment Share on other sites More sharing options...
Andrew Posted March 17 Share Posted March 17 @soar47 perfect thanks! Could you please try disabling the eject (and eject all) features in Alfred's Preferences > Features > System and let me know if the pause disappears? Link to comment Share on other sites More sharing options...
saor47 Posted March 17 Author Share Posted March 17 @Andrew It's gone! And I tried changing the keyword for eject to `test`, and than the `t` starts to cause the same problem. Link to comment Share on other sites More sharing options...
Andrew Posted March 20 Share Posted March 20 @saor47 I've seen a few cases of this over the past 6 months (after years of no problems). As part of the performance and efficiency improvements in the future 5.1 release, I've already preempted this as an issue and moved discovering the ejectable drives off of the main thread. saor47 1 Link to comment Share on other sites More sharing options...
Andrew Posted April 4 Share Posted April 4 @saor47 This should now be fixed in the 5.1 b2129 pre-release saor47 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now