During db2ldif of a master with replication agreements, a configuration item would leak memory.
<img alt="0001-Ticket-49508-memory-leak-in-cn-replica-plugin-setup.patch" src="/389-ds-base/issue/raw/files/8ea7c7e9370de88517f0e64e1afe15b7eca364761e757a8e86038b13965a878a-0001-Ticket-49508-memory-leak-in-cn-replica-plugin-setup.patch" />
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to review - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: review)
commit 3aa02b6 To ssh://git@pagure.io/389-ds-base.git 00d04b0..3aa02b6 master -> master
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Cherry-picked to 389-ds-base-1.3.9 as af724fb as a neat way of resolving merge issues while cherry-picking PR #50475.
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/2567
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.