named crashed with SIGABRT in assertion_failed()

StacktraceTop:
 assertion_failed (file=<optimized out>, line=<optimized out>, type=<optimized out>, cond=<optimized out>) at ../../../bin/named/main.c:232
 isc_assertion_failed (file=file@entry=0x7f2b23655798 "../../../lib/isc/mem.c", line=line@entry=1229, type=type@entry=isc_assertiontype_require, cond=cond@entry=0x7f2b236558bc "ctx->references == 1") at ../../../lib/isc/assertions.c:58
 isc__mem_destroy (ctxp=0x5626f0126c88 <ns_g_mctx>) at ../../../lib/isc/mem.c:1229
 isc_mem_destroy (mctxp=0x5626f0126c88 <ns_g_mctx>) at ../../../lib/isc/mem.c:2770
 main (argc=<optimized out>, argv=<optimized out>) at ../../../bin/named/main.c:1349

Status changed to 'Confirmed' because the bug affects multiple users.

The Error Tracker shows this bug occurring a lot:

http://errors.ubuntu.com/bug/1552801

Can I get your BIND configuration? Either to the bug, or privately to <email address hidden> if you are not comfortable posting it.

Nevermind.. I've reproduced it, and will be working on it. FWIW, the error is occurring during the daemon shutdown, though that's not really a big help. :/

Sorry to late answer.
This error happens on only the computer in home.
And what should I do to overcome it.

[Impact]

At shutdown, rather than terminating normally, named aborts with an assertion failure, pointing at a memory leak. This is confusing to users, and could potentially mask an actual memory-leak that could affect runtime operation. (The actual leaked memory is a control structure that is simply not deleted due to a bad patch migration.

[test case]
stop named, remove any related file in /var/crash, start it, and stop it again. no crash file should exist. If present, the trace shows main calling isc_mem_destroy (and we're dying in it's assertion that no memory has been leaked.)

[regression potential]
The root cause of the defect here was part of the chroot-init patch (no longer used) leaked into the random_1 patch when the patches were split up as part of going to quilt. The result was that the dst_lib_destroy() function was not called, causing the control structure for same to be "leaked" at shutdown. Other than all of the normal "a rebuild could cause anything to be broken", I don't see any issues from calling the function that upstream wants/needs t have called as we are shutting down. The worst case direct regression from from the change is that named would crash in a different way, at shutdown time.

[other info]

diff -urN bind9-9.10.3.dfsg.P4-8/debian/changelog bind9-9.10.3.dfsg.P4-8ubuntu1/debian/changelog
--- bind9-9.10.3.dfsg.P4-8/debian/changelog 2016-04-13 13:20:25.000000000 -0600
+++ bind9-9.10.3.dfsg.P4-8ubuntu1/debian/changelog 2016-04-26 19:17:47.000000000 -0600
@@ -1,3 +1,10 @@
+bind9 (1:9.10.3.dfsg.P4-8ubuntu1) xenial-proposed; urgency=medium
+
+ * Fix bad patch from when we switched to quilt. Closes: #820847 LP:
+ #1552801, #1549788, #1553460
+
+ -- LaMont Jones <email address hidden> Tue, 26 Apr 2016 16:30:06 -0600
+
 bind9 (1:9.10.3.dfsg.P4-8) unstable; urgency=medium

   [Timo Aaltonen]
diff -urN bind9-9.10.3.dfsg.P4-8/debian/patches/20_random_1.diff bind9-9.10.3.dfsg.P4-8ubuntu1/debian/patches/20_random_1.diff
--- bind9-9.10.3.dfsg.P4-8/debian/patches/20_random_1.diff 2016-04-13 13:20:25.000000000 -0600
+++ bind9-9.10.3.dfsg.P4-8ubuntu1/debian/patches/20_random_1.diff 2016-04-26 19:17:47.000000000 -0600
@@ -28,15 +28,6 @@
   else if (!strcasecmp(str, "cyclic"))
    mode = 0;
   else
-@@ -6923,8 +6925,6 @@
- if (server->tkeyctx != NULL)
- dns_tkeyctx_destroy(&server->tkeyctx);
-
-- dst_lib_destroy();
--
- isc_event_free(&server->reload_event);
-
- INSIST(ISC_LIST_EMPTY(server->viewlist));
 --- a/lib/bind9/check.c
 +++ b/lib/bind9/check.c
 @@ -147,6 +147,7 @@

Hello Ertan, or anyone else affected,

Accepted bind9 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.10.3.dfsg.P4-8ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Running 1:9.10.3.dfsg.P4-8, I see core files in /var/crash. Upgrading to 1:9.10.3.P4-8ubuntu1 (from xenial-proposed) I no longer see the error (other than during the upgrade, when -8 shuts down for the last time.)

Thanks

I also confirm that bind9 from xenial-proposed resolved this bug.

Last a few day, I haven't seen this problem.
Thanks

This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-9

---------------
bind9 (1:9.10.3.dfsg.P4-9) unstable; urgency=medium

  * Fix bad patch from when we switched to quilt. Closes: #820847 LP:
    #1552801, #1549788, #1553460
  * freshen patch to remove fuzz.

 -- LaMont Jones <email address hidden> Tue, 26 Apr 2016 15:17:58 -0600

This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-8ubuntu1

---------------
bind9 (1:9.10.3.dfsg.P4-8ubuntu1) xenial-proposed; urgency=medium

  * Fix bad patch from when we switched to quilt. Closes: #820847 LP:
    #1552801, #1549788, #1553460

 -- LaMont Jones <email address hidden> Tue, 26 Apr 2016 16:30:06 -0600

The verification of the Stable Release Update for bind9 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.