Details
-
Bug
-
Resolution: Incomplete
-
P2: Important
-
None
-
5.14.2, 5.15.0
-
None
-
Linux arch
Description
Shared QNetworkAccessManager "nam"
QNetworkReply *reply1 = nam->get(...);
connect(reply1, finished, slot(onFinished))
connect(reply1, destroyed, SLOT(onReplyDestroyed)
reply1->abort()
within onFinished call reply1->deleteLeter
within onReplyDestroyed verify that the reply has been destroyed and save the address of the reply1 (and print it on console)
QNetworkReply *reply2 = nam->get(another url)
- I see that the pointer address printed above is the same as the new one
- reply2 receives a message that was requested in reply1, that evidently arrives after reply1 had been aborted and destroyed
Somehow QNetworkAccessManager must mess up two subsequent gets and mix references to old and new reply.