[SERVER-49121] Investigate why fork() is called after creating threads Created: 25/Jun/20  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 4.5 Required
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Ryan Egesdahl (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-82516 Complete TODO listed in SERVER-49121 Needs Scheduling
Assigned Teams:
Server Development Platform
Participants:

 Description   

in SERVER-48933, we had to add a die_after_fork=0 setting to TSAN so we could run some of the tests. We should not have needed to add that flag because forking after creating new threads can cause lock issues. We need to find out why this is happening during those tests and change the behavior if possible.


Generated at Thu Feb 08 05:18:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.