1
0
Fork 0
mirror of https://github.com/yshui/picom.git synced 2024-10-27 05:24:17 -04:00
picom/tests/configs
Yuxuan Shui 9332cba8df core: delayed handling of root ConfigureNotify
Previously, root ConfigureNotify is handled immediately, by resetting
the backend, which in turn releases all the window images. This puts all
the windows into a state where they don't have images attached, which
they really should be in when the screen is redirected.

(To expand a little, a window without images should only exist if:
    * It's an unmanaged window.
    * Screen is unredirected.)

Normally, this kind of window could be fine, as the next render phase
will re-acquire images for them. However, if a window in this state is
destroyed with fading enabled, then the render phase won't try to
acquire images for it, causing it to go into the main rendering function
without images attached, and trigger an assertion.

This commit delays the handling of root ConfigureNotify until the render
phase. This way, the images will be immediately re-acquired after they
are released, thus prevent this problem from happening.

Also adds a testcase for this.

Fixes #357

Signed-off-by: Yuxuan Shui <yshuiv7@gmail.com>
2020-03-31 05:20:56 +01:00
..
empty.conf tests: support specifying config files for tests 2019-09-23 21:22:17 +01:00
issue239.conf tests: add test case for #239 2019-09-23 21:36:09 +01:00
issue239_2.conf tests: add testcase for #239, bug number 2 2019-09-28 23:23:24 +01:00
issue239_3.conf tests: add testcase for another case of #239 2019-11-18 20:53:49 +00:00
issue357.conf core: delayed handling of root ConfigureNotify 2020-03-31 05:20:56 +01:00