#1899 resolv-tests failing with memory leak
Closed: Fixed None Opened 9 years ago by yelley.

After doing a fresh "git clone" from master, the output (attached) of running chmake indicates that the resolv-tests have failed.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.0
rhbz: => 0

I just hit the same issue, and I probably found the cause - the resolv tests are leaking when I have the AD nameserver address in resolv.conf, when I comment this one out, the resolv tests work correctly.

cc: => okos@redhat.com

In file nslookup.txt, you can see that second resolving
of addres "redhat.com" takes real 0m1.103s. It is very long time. The reason is, that response was obtained from second name server.

I increased free_tv and terminate_tv timers from 1sec -> 2sec and then resolv-test did not fail.

What is the proposed fix for this issue? Should we raise the timers?

changelog: =>

We should fix either the tests or the resolver to not leak and survive even timeout properly.

Fields changed

milestone: SSSD 1.10.0 => SSSD 1.10.1

Fields changed

owner: somebody => mzidek

Moving tickets that didn't make 1.10.1 to the 1.10.2 bucket.

Moving tickets that didn't make 1.10.1 to 1.10.2

milestone: SSSD 1.10.1 => SSSD 1.10.2

Fields changed

patch: 0 => 1

resolution: => fixed
status: new => closed

Fields changed

changelog: => N/A, just a bugfix

Metadata Update from @yelley:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.10.2

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2941

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.

Login to comment on this ticket.