Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
5.15.2
-
None
-
Windows
Description
I have received reports from a couple users of my software - a very small portion, but probably half a dozen by now - that the software crashes. The crash occurs every time my program runs on these particular computers, and it happens at the following call stack:
04d3e0bc 56294519 ffffffff 03a869e0 03a94598 Qt5Core!QBasicMutex::lockInternal+0xa0 04d3e0d0 5b493031 03a869e0 03a94598 04d3e154 Qt5Core!QMutex::lock+0x59 04d3e0ec 5b4ec6ba 03a92d30 03a94598 56415822 Qt5Network!QNetworkConfigurationManagerPrivate::configurationAdded+0x51 04d3e0f8 56415822 03a869e0 00000000 00000007 Qt5Network!QNetworkConfigurationManagerPrivate::qt_static_metacall+0xba 04d3e114 5641425d 03a869e0 90d3ddc0 03a94598 Qt5Core!QMetaCallEvent::placeMetaCall+0x52 04d3e154 563f2255 03a94598 03a869e0 03a946d8 Qt5Core!QObject::event+0x10d 04d3e164 563f219c 03a869e0 03a94598 90d3dd38 Qt5Core!QCoreApplicationPrivate::notify_helper+0x55 04d3e1ac 563f3dc7 03a869e0 03a94598 90d3de80 Qt5Core!QCoreApplication::notifyInternal2+0xac 04d3e214 564336e0 03a946f0 00000000 03a946d8 Qt5Core!QCoreApplicationPrivate::sendPostedEvents+0x207 04d3e228 564322a7 90d3c258 03a65220 03a15f20 Qt5Core!QEventDispatcherWin32::sendPostedEvents+0x30 04d3fecc 563ee903 00000024 90d3c380 03a8da28 Qt5Core!QEventDispatcherWin32::processEvents+0x67 04d3ff14 5629240d 00000000 90d3c3d8 03a8da28 Qt5Core!QEventLoop::exec+0x1a3 04d3ff4c 56293f6c 90d3c3e4 56293e10 56293e10 Qt5Core!QThread::exec+0x9d 04d3ff70 7767fa29 03a526c1 7767fa10 04d3ffdc Qt5Core!QThreadPrivate::start+0x15c 04d3ff80 77ca7a9e 03a8da28 8f0560b9 00000000 kernel32!BaseThreadInitThunk+0x19
I have experimented with this problem and determined that in order for the program not to crash, I must never construct any Qt network classes, particularly, QNetworkAccessManager. In other words, it's not an attempt to actually communicate over network that cases the crash, it's the simple act of creating a QNetworkAccessManager object.
I'm pretty sure that the problem appeared in Qt 5.15, but I have not verified that.
Attached is the system report on network adapters from one of these systems. I will add more if I manage to obtain similar reports from other customers with the same problem.
