Due to the bug related to the 'new syntax' signal/slot connections, it's unfortunately possible to have a connection not deleted properly by the moment children objects get deleted. Then, as a result, in e.g. QSslSocket's destructor the socket will change its state, triggering the (now deleted) UI elements' access. Note - the original bug was reported, the patch (only possible?) was not accepted. Fixes: QTBUG-83659 Change-Id: I2965532485bcd46f93f8449e4d0a30da92b572c5 Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> |
||
|---|---|---|
| .. | ||
| certificateinfo.cpp | ||
| certificateinfo.h | ||
| certificateinfo.ui | ||
| encrypted.png | ||
| main.cpp | ||
| securesocketclient.pro | ||
| securesocketclient.qrc | ||
| sslclient.cpp | ||
| sslclient.h | ||
| sslclient.ui | ||
| sslerrors.ui | ||