#50610 memory leak in dbscan
Closed: wontfix 2 years ago by spichugi. Opened 2 years ago by lkrispen.

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


Metadata Update from @mreynolds:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Issue set to the milestone: 1.4.2

2 years ago

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

2 years ago

Metadata Update from @spichugi:
- Issue status updated to: Open (was: Closed)

2 years ago

Metadata Update from @spichugi:
- Issue assigned to spichugi

2 years ago

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

2 years ago

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

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)

2 years ago

There are failures in the nightly tests: suites/replication/changelog_test.py fails with

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)

2 years ago

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

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

2 years ago

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.

Thank you for understanding. We apologize for all inconvenience.

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

a year ago

Login to comment on this ticket.

Metadata