dbscan uses the REALLOC flag when doing database access, so when iterating thru a database keys and data will be freed, except for the last one.
This is a minor issue, but in ASAN builds dbscan then returns an error and the tests using it will fail.
PR ready
Fixed by Ludwig
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.2
https://pagure.io/389-ds-base/pull-request/50611
Metadata Update from @vashirov: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @spichugi: - Issue status updated to: Open (was: Closed)
Metadata Update from @spichugi: - Issue assigned to spichugi
Metadata Update from @spichugi: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1758469
More leaks are present that involve dbscan execution (the issue happens on instance restart though).
Steps to Reproduce: 1. Rebuild 389-ds-base with ASAN 2. Run the following tests that are using dbscan: tests/suites/password/regression_test.py::test_unhashed_pw_switch tests/suites/replication/encryption_cl5_test.py::test_algorithm_unhashed[AES]
Actual results: ASAN reports memory leak
Expected results: No memory leak in dbscan
https://pagure.io/389-ds-base/pull-request/51075
bc789a9..d45d8bd master -> origin/master 21aa9ab..b940d05 389-ds-base-1.4.2 -> 389-ds-base-1.4.2 b91683b..0222c25 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
Metadata Update from @spichugi: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
There are failures in the nightly tests: suites/replication/changelog_test.py fails with
suites/replication/changelog_test.py
E ldap.OPERATIONS_ERROR: {'desc': 'Operations error', 'info': 'Failed to close changelog; error - -1'}
Metadata Update from @vashirov: - Issue status updated to: Open (was: Closed)
d45d8bd..431aba8 master -> origin/master 469e141..0396340 389-ds-base-1.4.2 -> 389-ds-base-1.4.2 280ba7e..81eb7ab 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
https://pagure.io/389-ds-base/pull-request/51088
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/3666
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.