https://bugs.kde.org/show_bug.cgi?id=475648
Vlad Zahorodnii <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit| |https://invent.kde.org/plas | |ma/kwin/-/commit/d52ba8c3fe | |93f90e7754e641494c1d3bd81be | |c16 --- Comment #11 from Vlad Zahorodnii <[email protected]> --- Git commit d52ba8c3fe93f90e7754e641494c1d3bd81bec16 by Vlad Zahorodnii. Committed on 08/11/2023 at 14:09. Pushed by vladz into branch 'master'. wayland: Fix transaction cleanup with destroyed surfaces When sorting surfaces in the ancestor order we need to ignore null surfaces. In addition to that, we also need to properly handle the case where a transaction with dependencies is unlocked and it contains null surfaces. For example, if there are three transactions A -> B -> C, and the B transaction is unlocked, we cannot apply it until transaction A is applied. The readiness check is based on checking the first pending transaction of the surface. But if the surface is null, the check will be skipped, which is not ideal as transaction B can be applied before transaction A now. To address that, this change makes every transaction entry remember the previous transaction. With that, the readiness check can be performed even if the surface has been destroyed. M +17 -10 src/wayland/transaction.cpp M +5 -0 src/wayland/transaction.h https://invent.kde.org/plasma/kwin/-/commit/d52ba8c3fe93f90e7754e641494c1d3bd81bec16 -- You are receiving this mail because: You are watching all bug changes.
