If there is some sort of error in do_search - decoding or protocol errors - after the rawbase variable is allocated but before it is assigned to SLAPI_ORIGINAL_TARGET_DN in pb, the cleanup code will get the NULL variable from the pb and free it, leaking rawbase.
0001-Ticket-47774-mem-leak-in-do_search-rawbase-not-freed.patch 0001-Ticket-47774-mem-leak-in-do_search-rawbase-not-freed.patch
To ssh://git.fedorahosted.org/git/389/ds.git c5f22dd..9f174da 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 9426e07 Author: Rich Megginson rmeggins@redhat.com Date: Wed Apr 9 13:24:26 2014 -0600 b8297ad..1a39cf3 389-ds-base-1.3.0 -> 389-ds-base-1.3.0 commit 33bf4d42727804f5c10ce30834a2340c99cad459 Author: Rich Megginson rmeggins@redhat.com Date: Wed Apr 9 13:24:26 2014 -0600 44ecbbe..60c36f1 389-ds-base-1.3.1 -> 389-ds-base-1.3.1 commit 97f58ff4787ecb87780fde7245e354ec75e73125 Author: Rich Megginson rmeggins@redhat.com Date: Wed Apr 9 13:24:26 2014 -0600 48844b2..469c9b9 389-ds-base-1.3.2 -> 389-ds-base-1.3.2 commit b065515 Author: Rich Megginson rmeggins@redhat.com Date: Wed Apr 9 13:24:26 2014 -0600 844d09d..f573012 master -> master commit 1d5c6d6 Author: Rich Megginson rmeggins@redhat.com Date: Wed Apr 9 13:24:26 2014 -0600
Metadata Update from @rmeggins: - Issue assigned to rmeggins - Issue set to the milestone: 1.2.11.30
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1106
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.