In the work for ticket 47629 a memory leak was detected when repl sync did not free the operation structure. A fix would require access to connection management functions and is dependent on ticket 47661. To close 47629 and not forget the mem leak this ticket is created
Note: #47661 is set to 1.3.5.
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1206303
Metadata Update from @nhosoi: - Issue set to the milestone: 1.3.7 backlog
I just fixed a stack of leaks in repl sync. I'm going to close this issue, because it's "probably fixed", but if it re-occurs, we can open a new issue.
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to review - Issue close_status updated to: None
Metadata Update from @firstyear: - Custom field component reset - 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/1009
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.