Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
6.2.1
-
None
-
OS: Windows 10 Pro build 19044.1348; Qt 6.2.1
-
Windows
-
8
-
79a1523ed6 (qt/qtconnectivity/dev) 79a1523ed6 (qt/tqtc-qtconnectivity/dev) 9ef815af0a (qt/qtconnectivity/6.2) 9ef815af0a (qt/tqtc-qtconnectivity/6.2) 79a1523ed6 (qt/tqtc-qtconnectivity/6.3) 1806578f2e (qt/tqtc-qtconnectivity/5.15)
-
Team 1 Foundation_Sprint 48
Description
When a QBluetoothSocket which was previously connected is deleted, it seems to be possible that the application occasionally crashes with assertion:
ASSERT: "false" in file C:\Users\qt\work\qt\qtconnectivity\src\bluetooth\qbluetoothsocket_winrt.cpp, line 206
It seems that even though SocketWorker::close() in qbluetoothsocket_winrt.cpp cancels the asynchronous read, the SocketWorker::onReadyRead() function may nevertheless get called after the SocketWorker object has already been destroyed.