Sonoma 14.1 on new MacBook Pro with lots of RAM - QS 2.4.1 gets unresponsive 8-10 times daily #2988
Open
3 tasks done
Comments
|
I now suddenly usually have the crash reporting come up so I send in the crash log - here is the latest one: Report |
|
Same here: since Sonoma, Quicksilver is very often hanging on my MBP. I also fear it is responsible for my keyboard input to freeze very often. Never had such trouble before, I am considering getting back to previous OS because of this, but would much rather see this problem solved of course. |
|
I’ve sent at least 10-15 crash logs over the last days - crashes now sometimes display them. But so far no word from anybody on what might be going on. |
|
Sorry all. This is one of a long list of show-stopper Sonoma bugs. I'm the most junior member of the team and am trying to learn objc as I go, and I may be the only one running Sonoma, so things will be slow going for the foreseeable future. |
|
Thank you for replying. Let us know if we can do anything to help. |
|
hi n8henri — thanks for your response. Totally understand — also available if I can be of help. Hopefully we can muddle along restarting as we go. Question — have you received the crash logs I sent in? Do you want me / us to continue forwarding them? |
@alland138 The crash logs are anonymized, collected, and stored. I have 118 reports from Nov 2023 so far; I presume yours is one of them, but I'd need more info to be sure. Continuing to send them would be great, thank you. |
|
Hello Nathan
I imagine that something like 20% of those reports are from me … more will surely follow because QS crashes every hour or two, though there’s no discernible pattern to it
Best
Allan
…______________________

On Nov 24, 2023, at 15:32, Nathan Henrie ***@***.***> wrote:
Question — have you received the crash logs I sent in? Do you want me / us to continue forwarding them?
@alland138 <https://github.com/alland138> The crash logs are anonymized, collected, and stored. I have 118 reports from Nov 2023 so far; I presume yours is one of them, but I'd need more info to be sure.
Continuing to send them would be great, thank you.
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD2HVQEBHJGMGMOZKMF64ELYGC4YNAVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVHAZDOMRYG4>.
You are receiving this because you were mentioned.
|
|
Would you mind telling me your computer name or hostname so I can try to find which crash logs are yours? |
|
I don't see anything immediately obvious in your crash log above. Also, make sure to look through: https://docs.qsapp.com/documentation/faq#quicksilver-crashes-how-do-i-fix-it My guess is that your crashes will get figured out much more quickly if you go through things yourself (and hopefully report back) -- clearing caches and disabling plugins is where I'd start. |
|
Hi I just had a crash (in this case, the Apple crash log didn’t appear before the notification window to you was displayed (that happens sometimes — actually sometime no window at all appears and I just have to force quit.
To make it easy to identify my message, here’s what it contained. My exception is that you’ll be able to see identifying data in the data that accompanies the message and that will let you see all the logs I have sent:
Hi Nathan - here's the report from the latest crash — I'll send you a note now so that you can definitively identify my crash reports. In this case, though the crash log window didn't display, though i assume the data will come through to you directly anyway. Best, Allan
BTW, I have tried the cache cleaning and permissions fix routines repeatedly with Sonoma Cache Cleaner but no improvements from doing that. I’ll try the plug-ins but, frankly, I’m not overly hopeful .. still maybe I get lucky …
…______________________

On Nov 25, 2023, at 16:12, Nathan Henrie ***@***.***> wrote:
I don't see anything immediately obvious in your crash log above.
Also, make sure to look through: https://docs.qsapp.com/documentation/faq#quicksilver-crashes-how-do-i-fix-it
My guess is that your crashes will get figured out much more quickly if you go through things yourself (and hopefully report back) -- clearing caches and disabling plugins is where I'd start.
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD2HVQHPN4C4WANFQ5C7RCDYGIKGXAVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGM3DQMZZGQ>.
You are receiving this because you were mentioned.
|
|
(Sonoma still) Today I clicked on the Quicksilver icon, then I couldn't type a key in iTerm2 or Monitor anymore. |
|
Interesting — I’ve never seen other apps apparently impacted. Only symptoms I observe is QS becoming unresponsive and requiring a force quit then relaunch or QS crashing.
…______________________

On Nov 27, 2023, at 14:28, OM ***@***.***> wrote:
(Sonoma still) Today I clicked on the Quicksilver icon, then I couldn't type a key in iTerm2 or Monitor anymore.
I killed the Quicksilver process in Monitor with the mouse, and then could access the keys again.
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD2HVQH5XJE4BRLK3HJ7P7DYGSIOXAVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRXHAZTGNRZGE>.
You are receiving this because you were mentioned.
|
|
This has happened several times here. I have now uninstalled QS as it was in the way big time, but totally regret having upgraded to Sonoma. I use QS mainly for the the keyboard shortcuts to launch app though, and found another way to do so: It's a bit of a pain to setup, and a bit slow, not as reliable/reactive as QS (when it works properly) so I'm still waiting for QS to get back on the stage. |
|
Brilliant — I will try to set this up for the weekend. It would certain eliminate the stress of the crashing. Many thanks for pointing to this solution — it may not be as elegant and quick as QS but from the look of it, it’ll solve the problem till QS is reliable again. A.
…______________________

On Nov 28, 2023, at 10:17, OM ***@***.***> wrote:
This has happened several times here.
I right click on QS icon in the menu bar, get nothing and basically loose the keyboard. Not all of it though, as I can still Cmd+Tab to switch apps.
It's not really impacting other apps, more like stilling the keyboard, which makes sense as QS is always listening for its keyboard shortcuts I guess.
I have now uninstalled QS as it was in the way big time, but totally regret having upgraded to Sonoma.
I use QS mainly for the the keyboard shortcuts to launch app though, and found another way to do so:
https://www.idownloadblog.com/2021/01/15/launch-app-keyboard-shortcut-mac/
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD2HVQDVKGWMKDCJ6M7BB23YGWT35AVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRZGQYDINJQGE>.
You are receiving this because you were mentioned.
|
|
Update — I updated to MacOS 14.1.2 — and around that time the continuous crashing seems to have stopped ... the funny thin is that I can’t say exactly when it stopped but obviously the lack of crash logs from me will confirm it. I also can’t confirm that the OS update brought the stability but what I do know is that I don’t have the continual crashing any more and there’s nothing that I can point to as the cause of the improvement. Hopefully this will last! |
|
Very weird. Will leave this open for the moment in case it comes back -- hopefully 14.1.2 fixed something? |
|
I updated to 14.1.2 too; I used AppCleaner to uninstall Quicksilver, and reinstalled it. |
|
@OlivierMartineau I'm not totally sure that I understand what you mean, but maybe. I've experienced a similar bug for quite a while in which the keyboard text seems to disappear (in particular when I'm coding in Terminal.app while fullscreen), but I think the text is actually just be going to the wrong window (instead of the one displayed) -- but it seems that the keyboard is nonfunctional. For me, I think this is a MacOS bug, as it happens frequently when QS is not running at all. I usually have to switch Spaces a few times and click on a different window or two to get things working properly again. When you're describing right clicking on the QS menu icon -- do you mean as if to get the context menu shown below? 
If so, that seems to be working fine for me. I'm not familiar with AppCleaner. Deleting Quicksilver, You might try running this command in Terminal: If you've done all that and you're still getting unusual behavior with right clicking the menu let us know, I'll keep trying to reproduce. |
|
Yes, the right (or left) click on the QS menu icon is the one on the upper bar, indeed. Makes QS steal my keyboard input. AppCleaner basically does what you describe. I have already lost my preferences indeed, but I'll be able to retrieve them if I ever want to on a backup. No clue what you line "Use Effects" does but it doesn't seem to change a thing here: QS fails the same. Even after uninstalling QS, I don't see the icon on the MacOS Deck. I guess AppCleaner hasn't wiped out all the QS-related files. |
|
Very weird. What interface are you using?
When you open Activity Monitor, is Quicksilver in red / marked as frozen?
Nate
…On Tue, Dec 5, 2023, at 6:22 AM, OM wrote:
Yes, the right (or left) click on the QS menu icon is the one on the upper bar, indeed. Makes QS steal my keyboard input.
It has never worked here since Sonoma. It was working perfectly before.
AppCleaner basically does what you describe. I have already lost my preferences indeed, but I'll be able to retrieve them if I ever want to on a backup.
I wanted to make sure it was not some settings that was bringing QS to its knees.
No clue what you line "Use Effects" does but it doesn't seem to change a thing here: QS fails the same.
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJNQDHXZGX76NPD5CKBOETYH4NYDAVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQG44DGMJXGU>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
What do you mean by interface? When I open Activity Monitor, Quicksilver is not marked as frozen. |
|
Sorry, not sure what else to call it. The Bezel interface, or Primer, or Nostromo... the "theme" that determines how QS looks. NateOn Dec 5, 2023, at 6:26 AM, OM ***@***.***> wrote:
What do you mean by interface?
When I open Activity Monitor, Quicksilver is not marked as frozen.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
|
Oh: didn't think the user input devices could have an impact. |
|
Hi Nathan
For whatever reason QS now seems to be more stable — I had a freeze this morning (had to force quit) but that meant it had run without crashing since I last updated you. And so far, it’s gone about 12 hours without freezing or crashing completely — so definitely major improvement in the situation.
Best
Allan
…______________________

On Dec 5, 2023, at 14:57, Nathan Henrie ***@***.***> wrote:
Sorry, not sure what else to call it. The Bezel interface, or Primer, or Nostromo... the "theme" that determines how QS looks. NateOn Dec 5, 2023, at 6:26 AM, OM ***@***.***> wrote:
What do you mean by interface?
When I open Activity Monitor, Quicksilver is not marked as frozen.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD2HVQG5D3YYPW57OGJT4GTYH4R5NAVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBQHA2DIMZYGQ>.
You are receiving this because you were mentioned.
|
Not sure who you're responding to, but this is not what I was talking about. You can choose an interface in your appearance settings. |
|
Oh, I must have misread your post, sorry. I have no way to check this as the app won't respond as soon as I click on the icon in the menu bar :( |
|
The crashing several times a day suddenly started again —- this is purely a subjective impression based on lots of trouble-shooting and QA experienced .... I have not been able to repro it at will. But I’m starting to get the impression that the problem may be related to running WhatsApp Mac ... because using it more over the last days seems to have co-related with increased crashing. I’ll keep an eye out and perhaps the others on this thread can confirm whether their experience is in some way similar ... |
|
Since MacOS Sonoma 14.2.1 update on Dec. 19th Quicksilver icon as reappeared in the menu bar. And it works perfectly so far, I'm very happy :) I now understand what Bezer/Primer refers to, by the way, and QS is set to Primer apparently here. |
Well that's a relief! |
|
With Sonoma 14.2 on a Macbook Pro M2, I'm finding quicksilver has either crashed or self-quit about 1-2 times per day at the moment. Wishing you luck in diagnosing this. |
|
I'm one of those submitting crash reports, sometimes multiple a day. QS always seems to self-quit when I'm away from the computer — on wake? on sleep — it rarely happens when I'm working. I have an automation in Keyboard Maestro that checks if Quicksilver is running on wake and if not, relaunches. Let me know if you can use any more info to help diagnose. |
|
Hi — would you mind sharing how you configured the Keyboard Maestro automation you mentioned in your posting? I might get it to help cope with the crashing (which I wish was only once a day … the number of daily crashes/freezes has increased again, it seems). Thanks
…______________________

On Jan 3, 2024, at 08:02, Ian ***@***.***> wrote:
I'm one of those submitting crash reports, sometimes multiple a day. QS always seems to self-quit when I'm away from the computer — on wake? on sleep — it rarely happens when I'm working. I have an automation in Keyboard Maestro that checks if Quicksilver is running on wake and if not, relaunches. Let me know if you can use any more info to help diagnose.
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD2HVQHX53K2N2M2HOXI7CTYMT67VAVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUHEZDSMRSGQ>.
You are receiving this because you were mentioned.
|
|
This image shows the KM automation and you can download it here
|
|
Brilliant — thanks very much
I'll install KM and get this going.Itll save lots of frustration as a workaround till the bug is swatted.
…______________________

On Jan 4, 2024, at 17:08, Ian ***@***.***> wrote:
This image shows the KM automation and you can download it here <https://www.dropbox.com/scl/fi/hyk6otwdtus99b5403ejw/QS-launch-on-wake.kmmacros?rlkey=wbrveqrfb80057weuk1ity2is&dl=0>
QS-launch-on-wake.jpg (view on web) <https://github.com/quicksilver/Quicksilver/assets/463305/d2aad390-7db4-4a05-bb04-cbb66c6c48c3>
—
Reply to this email directly, view it on GitHub <#2988 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BD2HVQGDQXLZKC3X3OTCBYLYM3HWPAVCNFSM6AAAAAA7CTE44KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZXGM2TOOJWGM>.
You are receiving this because you were mentioned.
|
|
In my environment, installing the Safari plugin eats up all the memory. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before submitting your bug report, please confirm you have completed the following steps
Bug description
There’s no apparent pattern or reproducible cause but QS just seems to freeze multiple times a day (i.e. unresponsive). Only way forward is to force quit and restart QS. Never had a problem with QS until I started running Sonoma - and I have no idea what’s causing this - there are no crashes generating logs or messages
Steps to reproduce
Running the computer and doing normal work — nothing that apparently triggers the unresponsive state
Expected behavior
I expect QS to run smoothly, as it has always run in the past
MacOS Version
Other
Quicksilver Version
2.4.1
Relevant Plugins
None
Crash Logs or Spindump
If you let me know what you’d like me to do i.e. describe steps you need taken, I’ll be glad to do it
Screenshots
No response
Additional info
Running Sonoma 14.1
The text was updated successfully, but these errors were encountered: