From each@isc.org Wed Feb 17 16:10:10 2016 CC: MIME-Version: 1.0 In-Reply-To: Content-Disposition: inline X-RT-Interface: API References: <56C321F1.3080905@redhat.com> <20160216180151.GB89140@isc.org> <56C47574.5040601@redhat.com> Message-ID: <20160217161010.GA4249@isc.org> content-type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) by bugs.isc.org (Postfix) with ESMTP id 7C28C71B5A8 for ; Wed, 17 Feb 2016 16:10:10 +0000 (UTC) Received: by bikeshed.isc.org (Postfix, from userid 10292) id 738FB216C3B; Wed, 17 Feb 2016 16:10:10 +0000 (UTC) Delivered-To: bind9-bugs@bugs.isc.org Subject: Re: [ISC-Bugs #41707] Recent change "improve performance of RBT (#41165)" magically broke dyndb User-Agent: Mutt/1.5.23 (2014-03-12) Return-Path: X-Original-To: bind9-bugs@bugs.isc.org Date: Wed, 17 Feb 2016 16:10:10 +0000 To: "Petr Spacek via RT" From: "Evan Hunt" RT-Message-ID: Content-Length: 647 On Wed, Feb 17, 2016 at 01:28:28PM +0000, Petr Spacek via RT wrote: > > I'm also looking into an intermittent reference leak that seems to > > happen sometimes when a dyndb driver is reloaded. That one's making > > slower progress. > > How do you detect the leak? I can try and have a look, too. An assertion failure when cleaning up memory contexts. But I wonder now if it was something I'd done wrong when building, because I haven't been able to get it to happen again this week. I have jury duty and haven't been able to focus much time on it. I'll let you know what I find out when I'm back. Meantime I'm resolving this ticket, thankis.