Crashing multiple times a day - have tried everything but still crashing

94 views
Skip to first unread message

Robin Miller

unread,
Jul 16, 2022, 7:46:32 PM7/16/22
to Quicksilver
I've been using Quicksilver daily for well over a decade, but in the last few months i've been struggling with it crashing multiple times a day. Generally when I get back to my computer after it's been unused for a couple hours, the first thing I have to do is relaunch Quicksilver and send the crash report.

I feel like I've tried everything:
- Kept up to date with latest versions for the past few months.
- Deleted preferences
- Deleted caches
- 'Reset preferences' via QuickSilver multiple times
- Rebooted computer

Hardware is an M1 MacBook Pro (16-inch, 2021),  running macOS Monterey 12.4.

I have no plugins in use.

The crash reports are always segfaults, for example:

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000bf21dbc320b0 -> 0x00003f21dbc320b0 (possible pointer authentication failure)
Exception Codes:       0x0000000000000001, 0x0000bf21dbc320b0
Exception Note:        EXC_CORPSE_NOTIFY

Any further ideas??

Thanks,
R

Rob McBroom

unread,
Jul 18, 2022, 8:45:33 PM7/18/22
to Quicksilver
On 16 Jul 2022, at 15:03, Robin Miller wrote:

> - Kept up to date with latest versions for the past few months.

I think the update system may have been broken in one or two recent releases, and a lot of crashes have been fixed. Make sure you’re on 2.4.0. If so, please share the full crash report. Thanks!

--
Rob McBroom

rsagall

unread,
Jan 10, 2023, 10:34:16 AMJan 10
to Quicksilver
I have the same problem - numerous crashes. It just crashed while I had this forum open. I wasn't typig at the time. It frequently crashes when I wake up the computer from sleep.

I have the latest version of QS, Mac OS, etc.

Otherwise it works great.

ihf

unread,
Jan 16, 2023, 7:57:04 AMJan 16
to Quicksilver
I'm seeing the same. Running v2.4.0 with Mojave and all was well until maybe a week or 2 ago. The only thing I can think of is that I installed Keyboard Maestro. Is there a problem between these apps?

Nathan Henrie

unread,
Jan 16, 2023, 5:04:41 PMJan 16
to ihf, Nathan Henrie
> Is there a problem between these apps?

I don't know of an issue a priori. Would you mind making an issue at GitHub?

Any crash reports you've found?

If you look through the issues, you might find an existing similar one we're working on -- do you happen to have the process manipulation plugin on / enabled? If so you might consider disabling it to see if that helps.

Nate
--
You received this message because you are subscribed to the Google Groups "Quicksilver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blacktree-quicks...@googlegroups.com.

ihf

unread,
Jan 18, 2023, 12:58:25 PMJan 18
to Quicksilver
QS has gone from being rock solid to crashing frequently. I have added an issue with a crash report on github.

ihf

unread,
Feb 11, 2023, 7:31:58 PMFeb 11
to Quicksilver
Pretty sure the problem is KM interfering with QS. I also find that when KM is running, QS often misses keystrokes at least when first activated. Has anyone else seen this (in addition to the frequent crashes)?

ihf

unread,
Feb 11, 2023, 9:34:02 PMFeb 11
to Quicksilver
Add Streamdeck as a possible cause for QS instability. Is anyone running Streamdeck and getting crashes or other strange QS behavior?
Message has been deleted
Message has been deleted
Message has been deleted

reid...@gmail.com

unread,
Mar 2, 2023, 5:41:17 PMMar 2
to Quicksilver
Having the same issue. Tried having QS use Rosetta, but... no dice. 

Nathan Henrie

unread,
Mar 2, 2023, 5:53:51 PMMar 2
to reid...@gmail.com, Nathan Henrie
Hi all -- I'm so sorry to hear about the issues.

It would be tremendously helpful to have these reports in GitHub issues. The GitHub template prompts users to provide necessary detail, without which I don't think we'll be able to keep track of any patterns that point towards the root issue.

I know it doesn't seem like much has been happening to address these crashes, but they are not forgotten. I *do* go through the list of issues on GitHub when I can. Currently I'm still trying to get the tests to pass, which will give us a much easier route for bisecting and hunting down issues like this going forward, because as is I hardly know where to start.

Please, if you can, for crashes, glitches, bugs, and feature requests, create an issue on GitHub either along with or instead of emails to the listserve. This is a great medium for general questions ("how do I?"), but I think issues like this are more likely to get marked as read and never seen again than conclusively addressed. 

Thanks to all for considering!

Nate
Reply all
Reply to author
Forward
0 new messages