https://bugs.kde.org/show_bug.cgi?id=466914
--- Comment #6 from Luca Bacci <luca.ba...@outlook.com> --- Thanks for the report, Bucior! Seems to be a different issue according to the stacktrace, most probably in KScreen. The stacktrace is very useful! :) KScreen::Osd keeps a reference to a LibKScreen::Output. When Osd instances are destroyed, their references to LibKScreen::Output instances are dropped, and that can cause their immediate destruction. Osd also subscribes as an observeer for its member LibKScreen::Output's destruction: https://invent.kde.org/plasma/kscreen/-/blob/v5.27.2/osd/osd.cpp#L33. The handler method is Osd::hideOsd() is executed, but at that time Osd is already in the process of being destructed... As for fixes, we may ::disconnect() in Osd's destructor. However I don't get why Osd observes its member object for destruction if it keeps a reference to it? -- You are receiving this mail because: You are watching all bug changes.
