https://bugs.kde.org/show_bug.cgi?id=397479
--- Comment #8 from David Edmundson <k...@davidedmundson.co.uk> --- More related but different bugs :( I've identified the source of the GTK bug that bothers me the most. We block so that we only send one configure request until we get a damage event, in an attempt to keep things synced. In some cases we send configure with the same size twice; this will cause no surface commit, and our lock holds indefinitely until we cause a repaint. I don't want to do the fix of addressing the requests we send, but instead making us more robust to blocking. Ideally by removing the blocks and just tracking configure/acks correctly. -- You are receiving this mail because: You are watching all bug changes.
