[SERVER-18045] create global lock manager in a mongo static initializer Created: 14/Apr/15 Updated: 14/Apr/16 Resolved: 24/Apr/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Quint Iteration 3.1.2 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The destructor logs the unused locks at process exit which may lead to undefined behavior. |
| Comments |
| Comment by Geert Bosch [ 24/Apr/15 ] |
|
Better to not log rather than avoiding finalization of the lock manager by making it static. |