yabai abort()s with ...pointer being freed was not allocated #543
Labels
bug
Something isn't working
Comments
|
Can you run with the |
|
@koekeishiya: Thanks for pointing this out. I have found the following messages in my error log from yesterday shortly after the crash: However, this is with debug logging still disabled hence probably not helpful in debugging. I have now enabled debug logging and hope to provide more information when the next crash occurs. Will keep you posted... |
koekeishiya
added a commit
that referenced
this issue
May 28, 2020
|
I've fixed the |
koekeishiya
added a commit
that referenced
this issue
May 28, 2020
Thanks for the swift action. I have pulled the latest master branch and now I get the following debug output when starting/re-starting yabai: Not sure if this is relevant to the issue you fixed, however, it started occurring after the update. Maybe I need to do something else after updating yabai? I am updating like this in my |
|
Nah that does seem relevant.. why don't I get these messages is beyond me. I'll look into it. |
|
This also appeared in the error log as I have seen another crash just now: The stack trace isn't really that useful unfortunately. Here the MacOS crash report: |
|
For completenes’s sake here is my #!/usr/bin/env sh
# auto update from HEAD
YABAI_CERT=yabai-cert sh -c "umask 0022 ; $(curl -fsSL "https://git.io/update-yabai")" &
# global settings
# -- enable debug output to help report issues
yabai -m config debug_output on
# -- mouse_follows_focus: When focusing a window, put the mouse at its center.
yabai -m config mouse_follows_focus off
# -- focus_follows_mouse: Automatically focus the window under the mouse.
yabai -m config focus_follows_mouse autofocus
# -- window_placement: Specify whether managed windows should become the first or second leaf-node.
yabai -m config window_placement second_child
# -- window_topmost: Make floating windows stay on top.
yabai -m config window_topmost on
yabai -m config window_opacity on
yabai -m config window_opacity_duration 0.0
yabai -m config window_shadow on
yabai -m config active_window_opacity 1.0
yabai -m config normal_window_opacity 0.60
yabai -m config split_ratio 0.50
yabai -m config auto_balance on
yabai -m config mouse_modifier fn
yabai -m config mouse_action1 move
yabai -m config mouse_action2 resize
# general space settings
yabai -m config layout bsp
yabai -m config top_padding 5
yabai -m config bottom_padding 5
yabai -m config left_padding 5
yabai -m config right_padding 5
yabai -m config window_gap 5
# specific space settings
# yabai -m config --space 9 layout float
# rules
yabai -m rule --add app="^kitty$" title='[[:space:]]+Terminal[[:space:]]+' sticky=on grid=4:4:1:1:2:2
yabai -m rule --add app="^kitty$" title='[[:space:]]Yabai[[:space:]]Reference[[:space:]]' sticky=on grid=4:4:1:1:2:2
yabai -m rule --add app="^Calculator$" manage=off sticky=on grid=4:4:1:1:2:2
yabai -m rule --add app="^Core Tunnel$" manage=off sticky=on grid=4:4:1:1:2:2
yabai -m rule --add app="^Messages$" manage=off sticky=on grid=4:4:1:1:2:2
yabai -m rule --add app="^FaceTime$" manage=off
yabai -m rule --add app="^System Preferences$" manage=off
yabai -m rule --add app="^Digital Colour Meter$" manage=off
yabai -m rule --add app="^ScreenFlow$" manage=off
yabai -m rule --add app="^World Clock Pro$" manage=off
yabai -m rule --add app="^Jabber$" manage=off
yabai -m rule --add app="^wallpaper$" manage=off
# signals
# -- update active space in menu bar
yabai -m signal --add event=space_changed \
action="open -g 'bitbar://refreshPlugin?name=space.sh'"
yabai -m signal --add event=window_destroyed \
action="yabai -m query --windows --window &> /dev/null || yabai -m window --focus mouse"
yabai -m signal --add event=application_terminated \
action="yabai -m query --windows --window &> /dev/null || yabai -m window --focus mouse"
## THE LAST LINE
echo `date -n "+%Y-%m-%d %H:%M:%S.%s"` "[YABAI] Configuration loaded..." |
koekeishiya
added a commit
that referenced
this issue
May 28, 2020
|
Would you mind trying the latest master? |
|
@koekeishiya: Just tried 4c48844 and can confirm that the issue were the following error was logged in debug mode is now gone: Will keep debug mode on, observing things, and follow up should there be any more issues in this area. Thanks a lot for looking into this so swiftly and looking at the implementation I share your frustration with how the API is designed. It really forces one to jump through hoops to get a seemingly straight forward task done safely. |
|
@koekeishiya: I believe you can close this bug as fixed. Should there be anything else I will re-open with additional information. |
|
I'll leave it open for a while. The changes made above should not really be tied to the original crash you had, as far as I could tell originally anyway. If you don't experience this issue for, lets say, a week, we can probably consider this resolved. |
|
Unfortunately this is not completely gone, just had another crash like this today: I still need to crank up debugging (foolishly disabled it), however here is the output of stderr: To be continued... |
|
Should be fixed on the latest master; reworked some of the process termination handling after #529. |
koekeishiya
added
the
addressed on master; not released
|
@koekeishiya: Thanks for addressing this. I am seeing a similar issue with limelight. Do you want me to file an issue in that repo? |
|
Sure you can do that. I’ll copy paste the changes necessary later.
… On 2 Jun 2020, at 15:24, Igor Böhm ***@***.***> wrote:
@koekeishiya <https://github.com/koekeishiya>: Thanks for addressing this. I am seeing a similar issue with limelight. Do you want me to file an issue in that repo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#543 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPDZV4IHC6CIQ3DW3MXTSTRUT4QFANCNFSM4NM3N5MQ>.
|
koekeishiya
removed
the
addressed on master; not released
unrevre
pushed a commit
to unrevre/yabai
that referenced
this issue
Jan 26, 2022
unrevre
pushed a commit
to unrevre/yabai
that referenced
this issue
Jan 26, 2022
unrevre
pushed a commit
to unrevre/yabai
that referenced
this issue
Jan 26, 2022
unrevre
pushed a commit
to unrevre/yabai
that referenced
this issue
Jan 26, 2022
…free'd twice upon termination
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am running the latest version of yabai:
In the past two days I have seen the below crash (once a day):
It is sporadic, and I am not entirely sure how to reproduce it. Let me know if there is anything I can do to improve the bug report.
The text was updated successfully, but these errors were encountered: