Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Unresponsive and using over 100% CPU #3011

Closed
3 tasks done
siracusa opened this issue Jun 25, 2024 · 1 comment
Closed
3 tasks done

[Bug]: Unresponsive and using over 100% CPU #3011

siracusa opened this issue Jun 25, 2024 · 1 comment

Comments

@siracusa
Copy link

siracusa commented Jun 25, 2024

Before submitting your bug report, please confirm you have completed the following steps

Bug description

When I woke my Mac from sleep this morning, Quicksilver was unresponsive and was using over 100% CPU. I took a sample:
Sample of Quicksilver.txt

I'm running macOS 14.5 (23F79). It looks like macOS 14 is not a choice in the OS pop-up.

Steps to reproduce

I don't know how to reproduce it. I just woke my Mac from sleep and found it this way.

Expected behavior

I expected Quicksilver to be responsive after waking my Mac from sleep.

MacOS Version

Other

Quicksilver Version

2.4.2 (4041)

Relevant Plugins

No response

Crash Logs or Spindump

No response

Screenshots

No response

Additional info

No response

@pjrobertson
Copy link
Member

Hey John,

Working on some spring cleaning and fixing up of QS. Just getting to this - it looks like it's to do with the Safari Plugin and scanning the history. There were a few deadlock problematic areas that will be cleaned up in an upcoming release. Thanks for sharing the spindump, if you see this again, please share any further spindumps you have. The more the better

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants