Details
-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
6.4.1
-
None
Description
As a result of the discussion in QTBUG-83387 it was realized that the invocation of the disconnect all Signals Method in QObject can cause unwanted side effects and even crashes.
Known crashes occur in context of the Qt accessibility implementation on Windows, where QObjects are tracked via the destroyed signal und disconnecting all signals causes dangling pointers.
I therefore suggest to deprecate this method, to add a more explicit disconnectAll method instead and maybe to add runtime warnings when used on QWidget/QQuickItem objects.
The side effects are documented, but using the "disconnect all" functionality is just too tempting for developers so the API should help to prevent issues like this.
Attachments
Issue Links
- resulted from
-
QTBUG-83387 EXCEPTION_ACCESS_VIOLATION_READ on windowHandle function on a window got from a QAccessibleWidget
- Closed