Skip to content

Potential mutex overload #40

Description

@ghirpara

AsyncRequestManager uses a single QMutex m_mutex to guard its whole shared state — the map of tracked requests, the pending queue, everything. Every operation that touches async request state takes this same lock: submit(), dequeueNext(), markRunning(), markCompleted(), cancelJson(), and now getStatusJson(), getResultJson(), listJson().

Because it's one mutex, only one of these can run at a time, across every HTTP worker thread and the main
thread's own async processing loop.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions