Details
-
Bug
-
Resolution: Incomplete
-
P2: Important
-
None
-
4.7.1
-
None
-
Ubuntu 10.04 LTS, 64bit. Qt 4.7.1 compiled from source
Description
When using a QNeworkAccessManager's get() function, created and executed in its own thread separate from the QML gui, about 25% of the time it locks up the GUI. This is most noticeable if you stop the application before finished() is called, and re-start it. Attached is a sample project that shows the issue, with a rotating QML rectangle so as to make the lock-up noticeable. Binary is included, however recompiling from source is recommended.
The lock-up of the GUI only happens for about 10-20 seconds, and continues even past when QNetworkAccessManager fires finished(). The thread which owns QNetworkAccessManager continues to spin on without any kind of blockage, it's just the GUI (which should be entirely separate from QNetworkAccessManager) that locks up. It does not spin, as it uses no cpu, it simply blocks for an indeterminate amount of time occasionally when calling get().
Attachments
Issue Links
- relates to
-
QTBUG-13645 Symbian: Connecting to network causes QML application framerate to drop considerably
- Closed