New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
memory leak with repl sync #1009
Comments
Comment from nhosoi (@nhosoi) at 2015-03-11 23:24:05 Note: 47661 is set to 1.3.5. |
Comment from nhosoi (@nhosoi) at 2015-03-26 23:07:03 Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1206303 |
Comment from nhosoi (@nhosoi) at 2017-02-11 23:06:46 Metadata Update from @nhosoi:
|
Comment from firstyear (@Firstyear) at 2017-02-13 04:24:52 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. |
Comment from firstyear (@Firstyear) at 2017-02-13 04:25:01 Metadata Update from @Firstyear:
|
Comment from firstyear (@Firstyear) at 2017-02-15 00:42:53 Metadata Update from @Firstyear:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/47672
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
The text was updated successfully, but these errors were encountered: