My KWIN fork where I work on features like per-output virtual desktops
262b49d713
Summary: This is a gotcha moment: 1. Create Surface with id 1 2. destroy that Surface 3. Create another Surface Now if in step 3 the id is by pure chance getting reused and also 1, the wl_resource pointer of the SurfaceInterface of step 1 and step 3 are the same. This is rather unexpected and causes problems. When creating a ShellSurface in step 1 and step 3 it would fail. KWayland finds a ShellSurface which was already created for the Surface. The same can happen with QtSurfaceExtensionInterface and PlasmaShellInterface which also go into error state. On client side this would trigger a protocol error and terminate the application. An easy way to reproduce is opening the file open dialog from within Kate multiple times. This change addresses this problem by setting the surface pointer in those classes to null when the parent Surface gets destroyed. Thus creating a new ShellSurface won't find the old referenced Surface any more. For ShellSurface and PlasmaShellSurface a test case is added which hit the condition without this change. For QtSurfaceExtension we don't have the client side, so we cannot really simulate the condition. Reviewers: #plasma_on_wayland Subscribers: plasma-devel Tags: #plasma_on_wayland Differential Revision: https://phabricator.kde.org/D1937 |
||
|---|---|---|
| src/wayland | ||