#50300 memory leak in automember plugin when automember group does not exist
Closed: wontfix by mreynolds. Opened by mreynolds.

Issue Description

1. 389-ds-base-1.3.9.1/ldap/servers/plugins/automember/automember.c:1631: alloc_fn: Storage is returned from allocation function "slapi_pblock_new".
2. 389-ds-base-1.3.9.1/ldap/servers/plugins/automember/automember.c:1631: var_assign: Assigning: "mod_pb" = storage returned from "slapi_pblock_new()".
6. 389-ds-base-1.3.9.1/ldap/servers/plugins/automember/automember.c:1659: leaked_storage: Variable "mod_pb" going out of scope leaks the storage it points to.
#  1657|           }
#  1658|           slapi_entry_free(group_entry);
#  1659|->         return rc;
#  1660|       }
#  1661|       slapi_entry_free(group_entry);

0a4ee32c2..37f919a79 master -> master

c01d34cf8..d55de4d59 389-ds-base-1.4.0 -> 389-ds-base-1.4.0

68f791e9a..502281ff6 389-ds-base-1.3.9 -> 389-ds-base-1.3.9

Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

Metadata Update from @mreynolds:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1691931

Metadata Update from @mreynolds:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

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/3359

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

Metadata