You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2023. It is now read-only.
I figured the obvious suspects were bad serialization, a sneaky nil somewhere, or threading. But I couldn't find any of those.
Eventually I took the stacktrace at its word - the fact it's doing string comparisons implies it's something to do with the key of the NSDictionary, nothing to do with the value.
I think this may have something to do with the binding code as well, given the presence of ___CFPrefsDeliverPendingKVONotificationsGuts_block_invoke. If I comment out the actual binder.bindShortcut(...) call it doesn't happen, but that may be a red herring. Oh, and the original crash happened when setting up the second keybinding. I.e. it works once, but fails after the first binding set up.
Anyway, I don't know if you want to investigate, feel free to close. I just figured it might at least help some poor soul googling for the same issue.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
After upgrading to MacOS monterey, I consistently saw the following crash in slinger, a window management app I maintain.
lldb shows the stacktrace as follows:
I figured the obvious suspects were bad serialization, a sneaky
nil
somewhere, or threading. But I couldn't find any of those.Eventually I took the stacktrace at its word - the fact it's doing string comparisons implies it's something to do with the key of the NSDictionary, nothing to do with the value.
Somehow I turned up this thread from 7 years ago: https://stackoverflow.com/questions/24208594/swift-string-manipulation-causing-exc-bad-access
It's slightly different, yet the same fix works - pass an NSString key instead of a swift
String
.Here's the actual fix I made to slinger: timbertson/Slinger.app@dc55f53
I think this may have something to do with the binding code as well, given the presence of
___CFPrefsDeliverPendingKVONotificationsGuts_block_invoke
. If I comment out the actualbinder.bindShortcut(...)
call it doesn't happen, but that may be a red herring. Oh, and the original crash happened when setting up the second keybinding. I.e. it works once, but fails after the first binding set up.Anyway, I don't know if you want to investigate, feel free to close. I just figured it might at least help some poor soul googling for the same issue.
The text was updated successfully, but these errors were encountered: