David Rosca 828a9a3cfb container: Fix crash when view unmaps + maps quickly ... Followup on 4e4898e90f. If a view quickly maps and unmaps repeatedly, there will be multiple destroyed containers with same view in a single transaction. Each of these containers will then try to destroy this view, resulting in use after free. The container should only destroy the view if the view still belongs to the container. Simple reproducer: couple XMapWindow + XUnmapWindow in a loop followed by XDestroyWindow. See #6605 (cherry picked from commit f92329701b0983ec41fec29d3abc5c751cbe4a28)		2022-01-07 19:36:27 +01:00
..
arrange.c	container: Move pending state to state struct	2021-02-16 22:05:00 -05:00
container.c	container: Fix crash when view unmaps + maps quickly	2022-01-07 19:36:27 +01:00
node.c	container: Move pending state to state struct	2021-02-16 22:05:00 -05:00
output.c	output: emit node::destroy event	2021-12-17 14:39:48 +01:00
root.c	sway: replace noop_output by fallback_output	2021-11-25 17:48:34 +01:00
view.c	view: Fix null dereference	2021-12-13 14:51:13 +01:00
workspace.c	sway: replace noop_output by fallback_output	2021-11-25 17:48:34 +01:00