Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Q
qtbase
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Labels
  • Merge Requests 5
    • Merge Requests 5
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Jobs
  • Commits
  • mer-core
  • qtbase
  • Merge Requests
  • !3

Merged
Opened Dec 30, 2015 by Slava Monich@slava
  • Report abuse
Report abuse

Fix the problem with QNetworkAccessManager getting stuck in NotAccessible state

  • Overview 2
  • Commits 3
  • Changes

It appears that QNetworkAccessManager can keep receiving queued signals even after it has cleared its reference to QNetworkSession and disconnected the slots. That can mess up networkAccessible state. Particularly, QNetworkAccessManager can get stuck in NotAccessible state and refuse to submit new network requests until the next online state change signal pulls it out of this state.

There still may be a possibility that a signal from an old QNetworkSession could arrive when QNetworkAccessManager has already switched to another QNetworkSession, but this scenario is probably broken by design, since for whatever reason QNetworkAccessManager is only tracking one QNetworkSession. In any case, it's far less likely than the scenario which I was trying to fix.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
0
Labels
None
Assign labels
  • View project labels
Reference: mer-core/qtbase!3