Thread-unsafe StopWatch instance is shared by multiple threads

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • ALL
    • Service Arch 2023-07-24
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The method NetworkInterfaceTL::ExhaustCommandState::make() uses the future construct which captures and reads ExhaustCommandState::stopwatch object.

      The problem is that in db_integration_test (src/mongo/db/exhaust_cursor_currentop_integration_test.cpp:358) this stopwatch object is created on a different thread. This is why TSAN is reporting a possible data race.

              Assignee:
              Jennifer Wang (Inactive)
              Reporter:
              Romans Kasperovics
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: