[SERVER-28388] Improve lifetime handling of diagnosticMessage from LDAP operations Created: 17/Mar/17 Updated: 06/Dec/17 Resolved: 10/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Spencer Jackson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Platforms 2017-04-17, Platforms 2017-05-08, Platforms 2017-05-29, Platforms 2017-06-19, Platforms 2017-07-10, Platforms 2017-07-31, Platforms 2017-08-21 |
| Participants: |
| Description |
|
LDAP search results contain a diagnostic message sent by the server. We extract this from ldap_get_options, but don't always free it. Ensure that we do. |
| Comments |
| Comment by Githook User [ 10/Aug/17 ] |
|
Author: {'name': 'Spencer Jackson', 'username': 'spencerjackson', 'email': 'spencer.jackson@mongodb.com'}Message: |
| Comment by Spencer Jackson [ 24/Mar/17 ] |
|
I've gone through this more carefully, and realized I was a incorrect about this. The diagnosticMessage is being returned, however there is a case where it gets leaked. I'm changing this ticket to fix this issue. |