https://bugs.kde.org/show_bug.cgi?id=406784
--- Comment #5 from Vlad Zagorodniy <vladz...@gmail.com> ---
When compositing is off, unconstrained_stacking_order contains a dangling
pointer (added by Workspace::restack()):
Client::destroyClient(this=0x560e5f07d1a0)
Workspace::addDeleted(c=0x560e5f06e3b0, orig=0x560e5f07d1a0)
Workspace::raiseClient(c=0x560e5e6cc830)
Workspace::lowerClient(c=0x560e5e6cc830)
Workspace::lowerClient(c=0x560e5e6cc830)
Workspace::restack(c=0x560e5f07d1a0, under=0x560e5e7a2510)
Workspace::raiseClient(c=0x560e5e6cc830)
Workspace::constrainedStackingOrder()
unconstrained_stacking_order:
- 0x560e5e7824a0
- 0x560e5e795eb0
- 0x560e5e7bfba0
- 0x560e5f07d1a0
- 0x560e5e7a2510
- 0x560e5e7dcf80
- 0x560e5f06e3b0
- 0x560e5e79df70
When compositing is on, KWin doesn't crash. Investigating it further.
--
You are receiving this mail because:
You are watching all bug changes.
