aboutsummaryrefslogtreecommitdiff
path: root/sway/sway-bar.5.scd
diff options
context:
space:
mode:
authorRyan Dwyer <ryandwyer1@gmail.com>2018-07-25 19:26:12 +1000
committerRyan Dwyer <ryandwyer1@gmail.com>2018-07-25 19:26:12 +1000
commitb14bd1b0b1536039e4f46fe94515c7c44e7afc61 (patch)
tree9c55f79248819337f9d5c4310896eb86c49a533c /sway/sway-bar.5.scd
parentcdc4ad2b4f6239607e8eb5e398891dd78bc5c7ea (diff)
Fix crash when closing last child of a tabbed container
The crash only occurs if the mouse cursor is above the tabbed container when the last child is closed. Introduced in 03d49490ccff3c5c81bea73622c8616fa61eb3dd, over a week ago and unnoticed until now :O The above commit changes the behaviour of a focus change. When you change focus, it sends pointer motion which makes the client set a new cursor image. We already had this behaviour for workspace switching, but this commit adds it for view switching too, such as in a tabbed container or when closing a view. The sequence of events that leads to the crash is: * The last child of a tabbed container unmaps, which triggers a `destroy` event before we've cleaned up the child or reaped the tabbed container. * The seat code listens to the `destroy` event and removes the seat container from the focus stack. As part of this, it decides to set focus to the parent (my fix alters this decision). * When setting focus to the new parent, the container motion is sent as per the previously mentioned commit. * The motion code uses `container_at`, which encounters the tabbed container and its child in a half destroyed state, and everything blows up from there. `con->parent` is needed because scratchpad containers don't have parents if they're hidden, so this probably fixes a crash when a hidden scratchpad container closes too. The `con->parent->children->length > 1` check should catch any cases where the parent is about to be reaped.
Diffstat (limited to 'sway/sway-bar.5.scd')
0 files changed, 0 insertions, 0 deletions