https://bugs.kde.org/show_bug.cgi?id=486948
--- Comment #10 from Adam L <new.plan4...@fastmail.com> --- (In reply to Vlad Zahorodnii from comment #9) > I looked into this crash for a bit but I don't understand how kwin could > crash (iiuc the EffectWindow is likely deleted). If you disable window > animation effects and just keep blur and background contrast effects > enabled, is there still this crash? I've tried toggling various window effects, but perhaps not tried turning off just the animation related ones. Given the crash occurs only very intermittently, it's been hard to know what might work and what's just luck. In general, the 'this' pointer of EffectWindow when shown in the backtraces looks like a reasonable value for an address, so it seems more likely that this might be a use of the pointer beyond its lifetime, rather than a use of an invalid pointer before the EffectWindow is created (we'd see nullptr anyway I believe, as it comes from a unique_ptr.get() in window->effectWindow()). I had a bit of a dig through the kwin code though and it seems like the plugins should drop all internal uses of an effect window ptr when they receive the EffectsHandler::windowDeleted signal. This signal comes only from a connection to Workspace::deletedRemoved, which itself is only emitted in one place: the final unref of a window that takes it to 0, which then immediately deletes the window (and the effect window with it). There doesn't seem to be any clear mechanism for this to get out of sync (i.e window deleted but EffectsHandler::windowDeleted not called), so my vague guess is perhaps there is an unbalanced ref/unref on a window somewhere, such the window gets deleted even whilst other classes think they've sufficiently ref'd it to prevent deletion. In particular, the animation related effects appear to rely more heavily on the ref/unref system, which I guess is why you're asking? I've tried creating/destroying windows in a tight loop and triggering various effects whilst doing so, but cannot recreate the crash, so whatever is causing this seems to be extremely niche. I'll try disabling animation related effects, but determining the lack of a crash is going to be a slow process -- You are receiving this mail because: You are watching all bug changes.
