-
Notifications
You must be signed in to change notification settings - Fork 285
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]: Random crashes in background #2886
Comments
I have the same issue on macOS 11.6.6 with QS 2.2.2 (4036). Seems to have maybe started after the most recent update as it's been rock solid for me before that. Mine crashes within 5 minutes of relaunching it everytime now. I have been submitting crash reports when I relaunch Quicksilver after a crash. If anything else is required to help investigate please let me know. |
Same on me. Quicksilver_2022-06-09-080028_Yangs-MacBook-Pro.txt |
Same here. QS crashes every day. I don't use any plugins and I gave it the permission it requires, even though it shouldn't require it as it doesn't need it to do its job. I'm not sure how or where to get crash reports with this version. I suspect it's also eating up massive resources before it crashes, but I haven't been able to verify it. On macos 11.6.6 reproduction is trivial and it just requires running the app long enough. 100% chance of crash within a day or two. |
It seems like virtually all of these reports have been from MacOS < 12. I haven't had any issues at all, in fact has been more stable than it's been the last few years ¯\_(ツ)_/¯
I'll take a closer look when not on mobile, but I wonder if this could be a problem specific to older OS?
|
Quicksilver crashed occassionally on macOS 12.4 too Translated Report (Full Report Below)Process: Quicksilver [47773] Date/Time: 2022-06-10 07:07:05.3494 +0800 Sleep/Wake UUID: E1DAFD1C-EA26-4ABD-9364-AF78C94A36DE Time Awake Since Boot: 780000 seconds System Integrity Protection: enabled Crashed Thread: 5 Dispatch queue: QSCatalogEntry scanQueue: QSPresetRunningProcesses Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0x3765c0c8cbc0 is not in any region. Bytes after previous region: 60429129272257 Bytes before following region: 44642950657088 Thread 0:: Dispatch queue: com.apple.main-thread Thread 1:: com.apple.NSEventThread Thread 2:: VDKQueue Watcher Thread Thread 3: Thread 4: Thread 5 Crashed:: Dispatch queue: QSCatalogEntry scanQueue: QSPresetRunningProcesses Thread 6: Thread 7: Thread 8: Thread 9: Thread 10: Thread 5 crashed with ARM Thread State (64-bit): Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Quicksilver","timestamp":"2022-06-10 07:07:10.00 +0800","app_version":"2.2.2","slice_uuid":"ad40466c-909f-3c04-b08f-95238e320bc3","build_version":"4036","platform":1,"bundleID":"com.blacktree.Quicksilver","share_with_app_devs":1,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.4 (21F79)","incident_id":"F3DC07FD-6E67-4EF3-B4F2-57676276A2D6","name":"Quicksilver"}
], ] |
Attempted fix at various crashes in #2886
Thanks for submitting the crash reports. I believe I was able to reproduce @interseb 's crash, and have attempted to fix it. @kzykx 's crash is slightly different, but I have found a fix for this. Can you please try running the latest Quicksilver-debug version which you can download from here: https://github.com/quicksilver/Quicksilver/actions/runs/2475313724 If you continue to see crashes, then please re-upload the crash reports here. Thanks |
Thanks @pjrobertson for your quick response, I install the debug version today and it seems everything is ok now. I will update the reports next Monday to make sure the bug is fixed. I tested QS 2.2.3 for 72h with no crashes, the bug is fixed in v2.2.3. |
@pjrobertson I installed the debug version and I haven't had a crash yet (over 24 hours). Previously it wouldn't run more than a few minutes, thank you! |
Thanks both for your feedback! We've just released Quicksilver 2.2.3, which has these fixes incorporated. I will close this issue now! |
Thanks @pjrobertson. Feels so good to be able to rely again on Quicksilver. You only realise how much you care about something when it goes missing .... |
Before submitting your bug report, please confirm you have completed the following steps
Bug description
Quicksilver randomly crashes when it is not in use. It will sometime crash after a few minutes, or after several days.
Nothing appears at the time of the crash, and it is only when trying to invoke it later that it shows missing.
This report is done following a previous report in Bug #2878.
I attach here several Diagnostic reports from crashes with version 2.2.1:main-2d7c97d (the debug version provided for Bug #2878 ) as well as with the latest 2.2.2 version.
Steps to reproduce
Expected behavior
Not crash
MacOS Version
macOS 11
Quicksilver Version
2.2.2
Relevant Plugins
Enabled plug-ins are:
Clipboard
Contacts
E-mail support
iTunes Plugin
Keyboard Triggers
Microsoft Office Plugin
Primer Interface
Safari
Shelf
Crash Logs or Spindump
Quicksilver DiagnosticReports.zip
Screenshots
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: