yabai: Crash in event tap
It seems quite frequently (a few times in my working day) that I’ll get a notification saying something about payload-scripting-addition (too brief to notice and read usually), and then any windows that I’ve swapped position, e.g. from a layout:
A |
--+ B
C |
if I’d swapped to:
A |
--+ C
B |
it will have reset to the original positions, maintaining only layout.
The last many lines of the error log are:
yabai: scripting-addition payload was already injected into Dock.app!
(perhaps that’s what the notification says too.)
which I assume is an error on restart, rather than an error that caused it to restart. There’s nothing between one occurrence of this line and the next.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 29 (11 by maintainers)
Commits related to this issue
- #276 #240 copy event rather than retain — committed to koekeishiya/yabai by koekeishiya 5 years ago
- #276 #240 fixed a subtle lock-free multithreading bug in event processing! — committed to koekeishiya/yabai by koekeishiya 5 years ago
- #276 #240 retain rather than copy — committed to koekeishiya/yabai by koekeishiya 5 years ago
@tsujp You can just open Console.app, go to Crash Reports and look for the recent crashes for yabai. Alternatively, if you’re a registered Apple Developer, you can download the Additional Tools for Xcode and use CrashReporterPrefs.app to enable Developer mode.
This crash is not about the scripting addition at all, this was just a guess by the original author. I’ve updated the title to better reflect the underlying issue.
If this is happening frequently to you, disable the brew service and run yabai manually through a terminal with the –verbose argument:
yabai --verbosefor debug output.When a crash occur, copy the last ~15lines of the terminal output here, together with the supplied crash log found in Console.app. macOS will by default provide a crash report for any application that uses the default signal handlers. If you don’t know where in Console.app to find the crash logs, a quick google search should suffice.