[SERVER-18662] Refactor SSLManager's Constructor for Better Memory Management Created: 26/May/15 Updated: 05/Feb/16 Resolved: 23/Jun/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Security |
| Affects Version/s: | 3.1.3 |
| Fix Version/s: | 3.1.5 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Spencer Jackson |
| Resolution: | Done | Votes: | 0 |
| Labels: | 32qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 5 06/26/15 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The current implementation of SSLManager's constructor allocates memory through OpenSSL and may cause a leak if one of the dozen or so uassert/masserts in the constructor are triggered. The short-term fix has been to add LSAN suppressions, this ticket is used to document any more comprehensive fixes. |
| Comments |
| Comment by Githook User [ 23/Jun/15 ] |
|
Author: {u'username': u'spencerjackson', u'name': u'Spencer Jackson', u'email': u'spencer.jackson@mongodb.com'}Message: |