resolv-tests failing with memory leak #2941

sssd-bot · 2020-05-02T12:50:47Z

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1899

Created at 2013-04-30 20:35:32 by yelley
Closed as Fixed
Assigned to mzidek

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

Comments

Comment from yelley at 2013-04-30 20:36:26

test output of chmake
139686.txt

Comment from dpal at 2013-05-02 15:14:21

Fields changed

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

Comment from okos at 2013-05-14 15:16:28

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

Comment from lslebodn at 2013-05-16 11:39:04

Output from nslookup
nslookup.txt

Comment from lslebodn at 2013-05-16 11:48:07

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.

Comment from okos at 2013-06-03 15:22:49

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

changelog: =>

Comment from jhrozek at 2013-06-03 15:26:54

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

Comment from jhrozek at 2013-06-13 16:48:30

Fields changed

milestone: SSSD 1.10.0 => SSSD 1.10.1

Comment from mzidek at 2013-07-09 20:44:03

Fields changed

owner: somebody => mzidek