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

QNetworkAccessManager doesn't recover when network is reconnected

    XMLWordPrintable

Details

    • c89d0f9d532a2719118614b9fa9b8efffbe12f2f (qt/qtbase/5.12.1) ced53c483da3b1d55850d2087d9a743983c8b944 (qt/qtbase/5.9)

    Description

      Steps to reproduce:

      • Run attached test case.
      • Disable the network using the network manager tray icon.
      • The in progress request fails with 'NetworkSessionFailedError'.
      • Subsequent requests fail with 'UnknownNetworkError'.
      • Reenable the network using the network manager tray icon.
      • Requests continue to fail indefinitely with 'UnknownNetworkError'.

      Expected behaviour:

      • Once the network is reenabled, subsequent requests should complete successfully.

      This bug does not happen (i.e. requests complete successfully once network is reconnected):

      • If libqnmbearer.so is disabled (by chmod'ing to 0).
      • On Windows (network enabled/disabled using 'Network Connections').

      Attachments

        1. log.txt
          1.0 kB
        2. main.cpp
          1 kB

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-71104 recursive loop in network access manager

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-49751 [qt-iOS] network module stops functioning after network was disabled and then re-enabled

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              lpotter Lorn Potter
              nesuan23@gmail.com nesuan23@gmail.com
              Votes:
              7 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes