Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-63852

getThreadName() should not crash

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 5.0.12, 6.0.2, 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • v6.0, v5.0
    • Service Arch 2022-05-16, Service Arch 2022-05-30
    • 2

    Description

      If getThreadName() is invoked before ThreadContextsInitialized is complete, a SIGSEGV will happen. The name is typically needed for debugging and logging purposes and should not cause a crash. This ticket is to implement a mitigation to SIGSEGV

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-64639 Stitch SDK hits invariant initializing ThreadContext

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-66456 remove ThreadContext

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-66385 Remove ThreadName's dependence on ThreadContext (& vice versa apparently)

          • Major - P3 - Major loss of function.
          • Closed
          split to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-66385 Remove ThreadName's dependence on ThreadContext (& vice versa apparently)

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              billy.donahue@mongodb.com Billy Donahue
              sergey.galtsev@mongodb.com Sergey Galtsev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: