Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-18190

QNetworkAccessManager or bearer management causing lock up of QML gui

    XMLWordPrintable

Details

    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

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              earthdomain Earth Domain (Inactive)
              malcom2073 Michael
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes