-
Bug
-
Resolution: Fixed
-
Not Evaluated
-
None
-
6.8.4, 6.9.1
-
None
Starting with Qt 6.8.4 and Qt 6.9.1, due to https://codereview.qt-project.org/c/qt/qtbase/+/633924 I have been getting
QObject::disconnect: wildcard call disconnects from destroyed signal of QTcpSocket::unnamed
Because of those lines https://codebrowser.dev/qt5/qtwebsockets/src/websockets/qwebsocket_p.cpp.html#_ZN17QWebSocketPrivate18releaseConnectionsEPK10QTcpSocket
Upon every WebSocket open/close
It can be easily reproduced with the QML WebSocketClient example
These warnings are quite annoying when having multiple WebSockets in an application as the warning will pop on every close or destruction
- duplicates
-
QTBUG-135959 tst_QWebSocket::moveToThreadNoWarning is failing
-
- Closed
-
- relates to
-
QTBUG-137032 QMenu uses disconnect with wildcards
-
- Reported
-
-
QTBUG-137424 QObject::disconnect: wildcard call disconnects from destroyed signal of QNativeSocketEngine::unnamed
-
- Reported
-
-
QTBUG-137720 QObject::disconnect: wildcard call disconnects from destroyed signal of QTcpSocket::unnamed
-
- Closed
-