Details
-
Bug
-
Resolution: Incomplete
-
P3: Somewhat important
-
None
-
4.7.0
-
None
-
Windows 7 ultimate 64bit running on a macbook pro through bootcamp. Probably all windows versions on any platform. The attached test application has only been confirmed to reproduce the bug with qt 4.7.0-RC1, but my project application has had it happen when compiled with 4.6.2 and 4.6.3 as well on a number of different windows versions/hardware platforms.Windows 7 ultimate 64bit running on a macbook pro through bootcamp. Probably all windows versions on any platform. The attached test application has only been confirmed to reproduce the bug with qt 4.7.0-RC1, but my project application has had it happen when compiled with 4.6.2 and 4.6.3 as well on a number of different windows versions/hardware platforms.
Description
Occasionally when recovering from sleep mode, neither the qnetworkaccessmanager or the qnetworkreply objects emit any signals. Its as if they are never processed and sent after qnam->get is called.
The attached timeOutTestApp executes get requests against a host that requires basic authentication. After the finished(QNetworkreply*) slot is called it sends another request 2 seconds later. The request is aborted 15 seconds after it is sent if there is no response in a slot connected to a QTimer::timeout() signal. The timeout value can be changed without affecting the outcome. I've tested with as much as 2 min.
Steps to reproduce:
1) Compile and run the timeouttestapp on a windows client against a host with basic authentication(not sure if the authentication part is necessary, but as my project application uses it the sample app does as well).
2) Put the computer in sleep mode (It has been reported to happen in my project application on a variety of windows platforms, though i have only been able to reproduce it on my laptop).
3) Wait 5-10? min, then resume the session. The amount of time in sleep mode does not seem to affect the result. I have seen it fail after only 2 min in sleep mode and also resume successfully after as much as 30 min in sleep mode.
4) At this point there seems to some randomness as more often then not this works as expected. That is that the app resumes and continues to send get requests and receive answers. But sometimes it does not seem as any requests are issued by the qnam and the requests are all aborted due to the custom timeout.
I would guestimate it happens once every 5-10 times i try to reproduce it.
note: All testing has been done using a wireless connection. Not sure if that has any relevance.