e30e358ce6
Amends 2c67d47ea15c6dc34cc20d8fbdb406efb19f11d7, after which we emitted the signal, as the setParent(nullptr) call in the destructor would call back into the QDockWidget::event override. That change was correct, but we are now emitted signals while in the destructor, after a potential subclass destructor was already completed. This crashed applications that had slots connected to those signals. While arguably an application problem (PMF connections need to be disconnected explicitly), we can avoid this regression by blocking the emission of that signal when already in the destructor. Fixes: QTBUG-136485 Pick-to: 6.9.1 6.8 6.5 Change-Id: I6d5e98136beedc94c22287ccfd1198dd80f4f95e Reviewed-by: Axel Spoerl <axel.spoerl@qt.io> (cherry picked from commit 7869593119ffaea6002e6668814af159a2077398) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>