Clean up JSThreadConfig data that leaks when using JSThreads

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.8.0-rc4
    • Affects Version/s: None
    • Component/s: JavaScript, Shell
    • Fully Compatible
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The concurrency tests introduced in SERVER-16196 use ScopedThreads to run workloads. These ScopedThreads (intentionally) leak JSThreadConfig data, which eventually leads to build failures on VMs with limited RAM.

      We need to delete the JSThreadConfig data to keep the memory footprint of the shell reasonable during the tests:

      https://github.com/mongodb/mongo/blob/9db6b7d7ad6e585f9bc9b0779db10d53535b4b68/src/mongo/scripting/v8_utils.cpp#L313-L317

      https://github.com/mongodb/mongo/blob/9db6b7d7ad6e585f9bc9b0779db10d53535b4b68/src/mongo/scripting/v8_utils.cpp#L323-L327

        1. SERVER-16394.js
          0.6 kB

            Assignee:
            Alvin Richards (Inactive)
            Reporter:
            Kamran K. (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: