Coverity analysis defect 145824: Thread deadlock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Server Programmability
    • ALL
    • Programmability 2025-08-18
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Thread deadlock

      Two threads will be stuck waiting forever if each holds a lock the other needs to acquire. Threads may try to acquire two locks in different orders, potentially causing deadlock
      /data/mci/9292c3def3822c0dfd66af88847bcc64/bazel_cache/004acac643584f695e6309f72694e5ad/execroot/_main/src/mongo/util/background.cpp:321: ORDER_REVERSAL 145824 Calling "unique_lock" acquires lock "mongo::<unnamed>::PeriodicTaskRunner._mutex". [Note: The source code implementation of the function has been overridden by a builtin model.]

              Assignee:
              James Bronsted
              Reporter:
              Coverity Collector User
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: