PolytreeDE
/
picom
mirror of https://github.com/yshui/picom.git
1
0
Fork 0
Code Releases Activity

core: always clear stale flags in destroy_backend 

Reference: https://github.com/yshui/picom/pull/546#discussion_r532054960

Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
This commit is contained in:
Yuxuan Shui 2020-11-28 19:31:43 +00:00
parent 862d96d609
commit e49ef2ccd8
No known key found for this signature in database
GPG Key ID: D3A4405BE6CC17F4
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
src/picom.c
View File

@ -402,16 +402,17 @@ static void destroy_backend(session_t *ps) {
}
if (ps->backend_data) {
if (w->state == WSTATE_MAPPED) {
win_release_images(ps->backend_data, w);
} else {
// Unmapped windows could still have shadow images.
// And they might have image stale flags set by events.
assert(!w->win_image);
win_clear_flags(
w, WIN_FLAGS_PIXMAP_STALE | WIN_FLAGS_SHADOW_STALE);
win_release_images(ps->backend_data, w);
}
// Unmapped windows could still have shadow images, but not pixmap
// images
assert(!w->win_image || w->state != WSTATE_UNMAPPED);
// Windows can still have stale flags set. For mapped windows,
// this can happen when destroy_backend is called before the stale
// flags are handled (e.g. when destroy_backend is called in
// session_destroy, or configure_root); for unmapped windows, this
// is because their stale flags aren't handled until they are
// mapped.
win_clear_flags(w, WIN_FLAGS_IMAGES_STALE);
win_release_images(ps->backend_data, w);
}
free_paint(ps, &w->paint);
}