[SERVER-16394] Clean up JSThreadConfig data that leaks when using JSThreads Created: 02/Dec/14  Updated: 03/Mar/15  Resolved: 19/Jan/15

Status: Closed
Project: Core Server
Component/s: JavaScript, Shell
Affects Version/s: None
Fix Version/s: 2.8.0-rc4

Type: Bug Priority: Major - P3
Reporter: Kamran K. Assignee: Alvin Richards (Inactive)
Resolution: Done Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File SERVER-16394.js    
Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

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



 Comments   
Comment by Githook User [ 10/Dec/14 ]

Author:

{u'username': u'dpercy', u'name': u'David Percy', u'email': u'david.percy@mongodb.com'}

Message: SERVER-16394 Fix JSThreadConfig leak
Branch: master
https://github.com/mongodb/mongo/commit/2f1f5af37b460c45e399ee734f4c24134b4ac352

Generated at Thu Feb 08 03:40:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.