[SERVER-36708] Back stdx::mutex with a critical section on windows in debug builds Created: 16/Aug/18 Updated: 06/Dec/22 Resolved: 24/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Mira Carey | Assignee: | [DO NOT ASSIGN] Backlog - Server Development Platform Team (SDP) (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | service_architecture_continuous_delivery | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Development Platform
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
Backing stdx::mutex with a critical section on windows would provide better traceability (by allowing the debugger to see who owns what lock). It's a cost, but for debug builds we could enable it (and switch over stdx::condition_variable to be a condition_variable_any, to accept our stdx::mutex in it's wait). |