https://bugs.kde.org/show_bug.cgi?id=426175
--- Comment #196 from Maik Qualmann <metzping...@gmail.com> --- I specifically debugged this WorkerObject class. Even if the analysis tools report an error here, everything in the order of destruction is OK. Right, the derived class is destroyed first. But then the "aboutToDeactivate()" function falls back to the base class and is then called during the destruction. Since the function is not implemented as a pure virtual function, everything is OK. The "this" pointer has no influence on the derived or basis class execution. Maik -- You are receiving this mail because: You are watching all bug changes.
